canonical: https://jentic.com/apis/pumpgtm.com/pumpgtm # PumpGTM API The PumpGTM API runs LinkedIn and X outreach from your own backend: it builds multi-step sequences, adds leads to them, and pauses or resumes them as revisions. It also covers people searches with review batches, X Plays that import and enroll review candidates, X follower eligibility checks, pending reply decisions, funnel and activity reports, and signed webhook subscriptions. A separate Partner API lets agencies create per-user workspaces, mint hosted LinkedIn connect links, and set monthly lead caps. ## For AI agents Create and revise outreach sequences, enroll leads from people searches or X Plays, decide pending replies, and read funnel and activity reports in a PumpGTM workspace. ## Scope Does not handle bulk email sending, CRM deal pipelines, or ad campaigns. Use for LinkedIn and X outreach sequences, lead review, and reply handling only. ## Capabilities - Create a complete outreach sequence with createSequence, then replace its steps as a new revision using expectedRevision - Pause or resume a sequence through PATCH `/sequences/{id}/status` and add people to it with POST `/sequences/{id}/leads` - Run a people-search Play, read the review batch, and record good-fit decisions that enroll candidates - Check whether leads follow a connected X account and resolve handles to numeric X IDs - Read pending replies and decide each one, then review the activity ledger and lead funnel report - Subscribe to signed webhook events and schedule a signed test ping - Provision partner end-user workspaces with a monthlyLeadCap and mint hosted LinkedIn connect links ## Use cases ### Agent-run outreach through Jentic A sales agent builds and runs outreach without the developer handing it a workspace key. Through Jentic it creates a sequence, adds leads, and later reads pending replies, while the developer's own Jentic One instance injects the WorkspaceKey bearer credential and rules limit which PumpGTM operations it may call. Example prompt: Search Jentic for 'create an outreach sequence', call POST /sequences with a name and steps, then POST `/sequences/{id}/leads` to add the first leads ### Reply triage Outreach only pays off when replies are handled. GET /replies returns pending replies and POST `/replies/{id}/decide` records a decision, with optional text and timing fields such as days, so an agent can draft and route answers for a human to approve. Example prompt: GET /replies with limit 20, then POST `/replies/{id}/decide` for each reply with the chosen decision ### People search to enrollment Prospecting starts with targeting. POST `/people/searches` creates or revises a people-search Play from targeting criteria, GET `/people/reviews/{batchId}` returns the candidates found, and POST `/people/reviews/{batchId}/decisions` records good-fit decisions and enrolls them into a sequence. Example prompt: POST `/people/searches` with targeting and run true, read GET `/people/reviews/{batchId}`, then POST the decisions with a sequenceId ### Agency multi-client operation Agencies running PumpGTM for many clients use the Partner API to create an end-user workspace with an externalUserId and monthlyLeadCap, mint a hosted LinkedIn connect link for that user to authorize their account, and poll the link until it completes. Example prompt: POST /users with externalUserId 'client-42' and monthlyLeadCap 500, then POST `/users/client-42/linkedin/connect-links` and poll GET `/users/client-42/linkedin/connect-links/{linkId}` ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/sequences` | Create a complete sequence | | POST | `/sequences/{id}/leads` | Add people to a sequence | | PATCH | `/sequences/{id}/status` | Pause or resume a sequence | | POST | `/people/searches` | Create or run a people-search Play | | GET | `/replies` | Read pending replies | | POST | `/replies/{id}/decide` | Decide a pending reply | | GET | `/reports/funnel` | Read the lead funnel | | POST | `/webhooks` | Subscribe to signed events | ## Key resources - **Sequences** — Create, revise, pause, resume, and add leads to outreach sequences - **Leads** — List, read, enrich, and remove leads, and supply per-person values for held steps - **People searches and reviews** — Targeted people-search Plays with review batches and enrollment decisions - **X Plays** — X follower eligibility, identity resolution, candidate import, and enrollment - **Replies and reports** — Pending reply decisions, funnel report, progress, and activity ledger - **Webhooks** — Signed event subscriptions with test pings - **Partner users** — Per-user workspaces, lead caps, and hosted LinkedIn connect links ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 61 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 61 / 100 - Developer Experience & Jentic Compatibility: 69 / 100 - AI-Readiness & Agent Experience: 44 / 100 - Agent Usability: 92 / 100 - Security: 60 / 100 - AI Discoverability: 64 / 100 - **View full report:** https://jentic.com/apis/pumpgtm.com/pumpgtm/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring PumpGTM by hand means handling its WorkspaceKey bearer token, two server bases for workspace and partner calls, the optional X-Eve-User routing header, and revision checks on every sequence edit. Through Jentic you install once, import PumpGTM from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** PumpGTM puts sequence, Play, and partner user ids in the URL path (`/sequences/{id}`, `/plays/{id}`, `/users/{externalUserId}`), so a rule can pin your agent to one sequence or one end user. You choose the operations it may call, so destructive ones like removing leads or disabling a partner user are not included unless you add them. - **Credential handling:** Your PumpGTM workspace key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'pause an outreach sequence' or 'read pending replies', and Jentic returns the matching PumpGTM operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **lemlist API** — Email and LinkedIn outreach sequencing platform - **Outreach API** — Sales engagement platform for sequences and prospect tracking - **Apollo API** — B2B contact and company database for prospect lists - **Hunter API** — Email finder and verifier ## FAQ ### What authentication does the PumpGTM API use? The PumpGTM API declares an HTTP bearer scheme named WorkspaceKey in its OpenAPI spec, carrying a workspace key. Partner accounts use their partner workspace key, and the optional X-Eve-Client and X-Eve-User headers select an end user. The partner signup operation needs no credential. Through Jentic, the key is stored encrypted by your own Jentic One instance and injected at execution time. ### Can I pause a PumpGTM sequence through the API? Yes. PATCH `/sequences/{id}/status` takes a required status field to pause or resume an existing sequence. To change its steps instead, PUT `/sequences/{id}` replaces them as a new revision and requires the expectedRevision you last read. ### What are the rate limits for the PumpGTM API? The OpenAPI spec does not state request rate limits. It does expose LinkedIn sending limits per account: GET `/linkedin/accounts/{accountId}/sending-limits` reads the daily invite cap and warm-up state, and the matching PATCH changes them. Check PumpGTM's developer documentation for API request limits. ### How do I add leads to a PumpGTM sequence through Jentic? Install Jentic One, import the PumpGTM API from the Jentic API Directory, and store your workspace key. Your agent searches for 'add people to an outreach sequence', Jentic returns POST `/sequences/{id}/leads` with its schema, and the agent calls it with the sequence id. To run it on your own infrastructure, install Jentic One from its GitHub repo. ### Is there a PumpGTM MCP server? You don't need an MCP server to give your agent PumpGTM. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it, discovering operations on demand rather than loading every tool definition into its context. ### Can I limit what my agent is allowed to do with the PumpGTM API? Yes. For example, write a rule that allows GET /replies, POST `/replies/{id}/decide`, and GET `/sequences/{id}` only for sequence 'seq_123', so the agent can triage replies and read that one sequence but cannot create sequences, perform X actions, or delete webhooks. Every call it makes is logged. ### Can the PumpGTM API act on X as my connected account? Yes. POST `/x/actions` follows, likes, or reposts as a connected account, taking a required action and target. GET `/x/accounts` lists the connected X identities, and POST `/x/eligibility` checks whether a set of leads follows a given account.