Apollo
Connect Apollo to search and enrich people and companies, and manage contacts, deals, sequences, tasks, and calls.
You end up with one Apollo API key string, shown once at creation, that you paste into PopMCP's API key field.
Paid plan required before this connector works
Nobody reviews anything at Apollo - the key is issued instantly - but Apollo gates which API endpoints a key can call by subscription plan. Apollo's docs state plainly that "Access to Apollo API depends on your Apollo plan", and its pricing FAQ lists API access under custom/enterprise plans.
- Typical wait
- None - the key is generated instantly. Any wait is a sales or upgrade conversation, not a review.
- Cost
- Apollo does not publish a per-endpoint API price, and its pricing page routes API access to custom plans quoted by sales, so there is no reliable public dollar figure to give. Budget for a paid tier plus Apollo credits, which API calls consume, and get the number from Apollo sales for your seat count.
- Blocked until approved
- On a plan without the access, the key exists but calls return 403 rather than failing at key creation. Master-key-only endpoints (Apollo's docs name listing users as one) and the broader write and search surface are what disappear, so the integration builds and authenticates fine and then fails at runtime on the specific endpoint you need.
- Works meanwhile
- A key can be created and tested on any plan, so auth plumbing, error handling, and request shapes are all buildable now. Probe each endpoint your connector actually calls with the key you have - a 403 tells you which ones need the upgrade before you commit to a plan.
Where to apply: Apollo web app > Settings > Integrations > API > API Keys > Create new key. Toggle 'Set as master key' for all endpoints, or select individual endpoints for a scoped key. Plan upgrades go through Settings > Plans and Billing or the Apollo sales team.
- The failure mode is a silent 403 at call time, not an error when you create the key - a key that looks fine can fail on the one endpoint you actually need. Test every endpoint before shipping.
- A key identifies the workspace, not a person, so Apollo cannot attribute usage to a teammate; rotate deliberately.
- Apollo restricts parts of the API surface for accounts registered with a personal email address rather than a work domain; if lookups return nothing on a free account, check the signup email before blaming the key.
- Endpoint access, rate limits, and credit cost per call all vary by plan, so a working integration can start failing after a downgrade.
- Accounts opened through Apollo sales must go back to sales to change plan - self-serve upgrade is not always available.
- Setup time
- 3 min
- Auth
- API credentials
- API base URL
- https://api.apollo.io/api/v1
- Rate limits
- Enforced per team across minute, hour and day windows. Roughly 50 calls per minute on Free and 200 on paid plans for standard endpoints, with higher search and enrichment allowances on paid plans.
Before you begin
- Apollo account on a plan that includes API access
- Permission to open Settings and the Integrations tab for your Apollo team
- A decision on master key (every endpoint) versus a scoped key
Get your credentials
Open Settings and the Integrations tab
Sign in to Apollo, click Settings at the bottom of the sidebar, then open the Integrations tab. Find the API card and click Connect.
Integrations
Connect Apollo to the tools your team already uses.
| Integration | Status | |
|---|---|---|
| SalesforceTwo-way CRM sync | Not connected | Connect |
| HubSpotTwo-way CRM sync | Connected | Manage |
| APIBuild against the Apollo REST API | Not connected | Connect |
The API card sits with the other integrations, not under profile settings.
Open the API keys list
Click API Keys on the Apollo API screen. The same list is at developer.apollo.io/#/keys.
API keys
Keys authenticate every request to the Apollo REST API.
| Name | Key | Access | Created | Status |
|---|---|---|---|---|
| Zapier importPeople Search only | ****9c14 | Scoped | Mar 4, 2026 | Active |
The Usage tab shows credits spent and the per-minute, per-hour and per-day call limits.
Create the key with full endpoint access
Click Create new key, fill in Name and Description, then turn on Set as master key. Click Create API key.
API keys
Copy the key before you leave the page
Click Copy on the confirmation panel. Paste the value into PopMCP's API key field and save the connection.
API keys
Existing keys can be regenerated or deleted from the same list.
Connect in PopMCP
Open your workspace, choose Apollo in the marketplace, and fill in the connect dialog:
| Field | What to enter |
|---|---|
| API keysecret | In Apollo go to Settings → Integrations → API → API Keys → Create new key. Toggle “Set as master key” for full coverage (recommended), or scope it to specific endpoints. Paste the key here. It's sent as the x-api-key header and stored encrypted; used server-side only. API access depends on your Apollo plan.Encrypted with AES-256-GCM on save and never shown again. |
PopMCP verifies the credential against Apollo immediately. On success the connection flips to Verified and its MCP tools are provisioned.
Verify it worked
PopMCP marks the Apollo connection Connected and the Apollo tool list appears. A first call such as a people search returns rows instead of an auth error.
Troubleshooting
401 Unauthorized
Why: The key was mistyped, truncated, or deleted in Apollo.
Fix: Create a fresh key under Settings, Integrations, API Keys and paste the whole string with no leading or trailing spaces.
403 Forbidden on some tools only
Why: The key is scoped and the endpoint behind that tool was not ticked, or the endpoint is master-key-only.
Fix: Edit the key's endpoint list, or create a replacement with Set as master key turned on.
403 on every call, including the health check
Why: Your Apollo plan does not include API access.
Fix: Upgrade the plan or ask Apollo to enable API access, then retry with the same key.
429 Too Many Requests
Why: Apollo rate limits per team across minute, hour and day windows.
Fix: Wait for the period named in the retry-after header. Limits are shared by everyone on your team rather than per key.