Apollo.io API in 2026: Endpoints, Credits, Rate Limits and How to Get an API Key

A developer's dashboard showing Apollo API endpoint cards for People and Organization enrichment, a credit counter ticking down, and a rate-limit gauge nearing its cap

Apollo.io API in 2026: Endpoints, Credits, Rate Limits and How to Get an API Key

Disclosure: Datamagnet publishes this article and sells a profile data API. Apollo.io details below come from Apollo's developer docs and its own website, checked on November 17, 2026. Apollo changes plans and limits often, so confirm them in your account before you budget.

The Apollo.io API is the REST interface to Apollo's database of 240M+ contacts and 30M+ companies, and to the records, sequences and calls in your Apollo workspace. You authenticate with an API key sent in the x-api-key header, and every call counts against your plan's credits and rate limits (Apollo docs, Authentication).

Key Takeaways

  • Create a key in Apollo under Settings > Integrations > API Keys. Keys are scoped to chosen endpoints by default, and a master key opens every endpoint.
  • People API Search is free (0 credits) but returns no emails or phone numbers. People Enrichment costs 1 to 9 credits per person, and waterfall phone lookups typically 8 to 25.
  • Free allows 600 calls a day. Paid plans get 1,000 enrichment calls a minute and 50,000 search calls a day, shared across the team.
  • All Apollo plans include basic API access, but Apollo's pricing page puts "advanced or custom integrations" on Custom plans, and reselling data needs a separate contract.
  • Apollo enriches from its own database. If you need a public profile read at the moment you call, see Datamagnet vs Apollo.

A developer's dashboard showing Apollo API endpoint cards for People and Organization enrichment, a credit counter ticking down, and a rate-limit gauge nearing its cap

How to Get an Apollo API Key

To get an Apollo API key, sign in as an admin, open Settings > Integrations > API Keys, and click Create new key. Name it, pick the endpoints it may call or set it as a master key, choose an integration type, then click Create API key and copy it. Apollo shows the full key once.

These are the steps from Apollo's Create an API Key guide:

  1. Launch Apollo and click Settings > Integrations > API Keys (the developer portal).
  2. Click Create new key.
  3. Give the key a name and a description that tells your team what it is for. Then select each endpoint the key may call, or toggle Set as master key to select all of them.
  4. Pick the integration type: Private (built for and used by one Apollo customer), Public (any Apollo customer can connect it) or Reseller (provides Apollo data to end users without each one connecting their own Apollo account).
  5. Click Create API key.
  6. Click Copy and store the key somewhere safe.

You must be an admin on the Apollo account, or hold a permission profile that allows it, to create keys (Apollo Developer FAQs).

Scoped key or master key?

A scoped key is the default. It works only on the endpoints you selected and returns a 403 on any other. A master key can call every endpoint, and a few endpoints, such as create call records and get a list of users, only accept a master key. Apollo recommends scoped keys and says to treat a master key "like a password" (Create an API Key; Authentication).

Test the key

Send GET https://api.apollo.io/api/v1/auth/health with your key in the x-api-key header. A working key returns {"healthy": true, "is_logged_in": true} (Test an API Key).

curl --request GET \
  --url 'https://api.apollo.io/api/v1/auth/health' \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY'

One detail surprises teams later. A key identifies the workspace, not a person, so every key request acts as the workspace's longest-standing active admin, who then owns any records you create (Authentication). Partners acting for other Apollo users need OAuth 2.0 instead. Deleting a key breaks every integration that uses it.

Apollo API Pricing

The Apollo API has no separate price. Access comes with an Apollo plan, and calls spend that plan's credits: 0 for people search, 1 per company enriched, and 1 per person plus 8 when a mobile number comes back. Apollo's May 2026 plan summary lists Basic at $49 and Professional at $79 per user a month, billed annually.

PlanPrice (billed annually)Credits per yearAPI rate limit, general endpoints
Free$090050/min, 600/day
Basic$49 per user/month30,000200/min, 2,000/day
Professional$79 per user/month48,000200/min, 2,000/day
Organization$119 per user/month, 3-user minimum72,000200/min, 6,000/day
CustomQuoteCustomContact Apollo

Prices and credits: Apollo's own Apollo vs ZoomInfo page (May 13, 2026), which says plans are billed annually and that monthly billing is also available on Basic and Professional. Rate limits: Apollo docs, Rate Limits. The live pricing page currently names Free, Basic, Professional and Custom and does not show dollar figures in its page text.

Credits are pooled across your team and granted at the start of each billing cycle. They "expire at the end of each billing cycle and do not carry over," including add-on credits you buy (Apollo Pricing FAQ). Add-on credits recur every cycle until you remove them.

A fair use policy also applies. Non-paying accounts with a verified corporate email are capped at 10,000 credits a month, and those without one at 100 (Apollo Pricing).

If your workspace is on a legacy plan, API credit costs may differ from the tables here. Apollo points you to Settings > Billing and credits > About credits for your exact rates (API Pricing and Credits).

Which Apollo Plans Can Use the API?

Every Apollo plan, including Free, includes at least basic API access, and most endpoints work on all accounts. The differences are rate limits, credits and a few gates. Free accounts need a work email for search, enrichment and record-retrieval endpoints, and Apollo's pricing page reserves "advanced or custom integrations" for Custom plans.

Apollo's docs state that "all Apollo plans include access to our API" and that "more advanced functionality is only available on certain plans" (Developer FAQs). The API overview adds that "most endpoints are available to all Apollo accounts" (Apollo API). Here is how that plays out:

  • Free accounts registered with a personal email can't use People API Search, People and Organization Enrichment, Organization Search or Get Complete Person Info. Each of those endpoint pages says it "requires an Apollo account registered with a work email address," and that paid accounts aren't affected.
  • Rate limits rise with the plan. Free is capped at 600 calls a day on every endpoint group. Paid plans get much higher enrichment and search limits (table below).
  • Developer tools can't exceed your plan. Apollo says the API, MCP and CLI "follow your Apollo permissions, plan access, and credit availability" (Developer FAQs).
  • Custom plans. Apollo's pricing FAQ says that "for more advanced or custom integrations, API access is available on Custom plans" (Apollo Pricing).
  • Reselling or exposing data to non-Apollo users "requires a custom contract with Apollo" (Developer FAQs).

What Endpoints Does the Apollo.io API Offer?

Apollo's API has two halves. The data half searches and enriches people and companies in Apollo's database, plus job postings and news. The workspace half manages your accounts, contacts, deals, lists, sequences, tasks, calls, emails and conversations. Every request goes to https://api.apollo.io/api/v1, authenticated with the x-api-key header.

These are the data endpoints, with the method, path and credit cost from each endpoint's reference page:

EndpointMethod and pathWhat it doesCredits
People API SearchPOST /mixed_people/api_searchFind net-new people by title, location, seniority and more. No emails or phones returned0
People EnrichmentPOST /people/matchMatch one person by email, name plus domain, or profile URL1, +8 with a mobile number
Bulk People EnrichmentPOST /people/bulk_matchUp to 10 people per request1 to 9 per person
Get Complete Person InfoGET /people/{id}Full record for a person ID1 per person
Organization SearchPOST /mixed_companies/searchFind companies with filters, up to 100 per page1 per page
Organization EnrichmentGET /organizations/enrichMatch one company by domain, website or profile URL1
Bulk Organization EnrichmentPOST /organizations/bulk_enrichUp to 10 companies per request1 per company
Organization Job PostingsGET /organizations/{organization_id}/job_postingsA company's open roles, up to 10,000 per page1 per page
News Articles SearchPOST /news_articles/searchNews about companies, up to 25 per page1 per page
View API Usage StatsPOST /usage_stats/api_usage_statsYour rate limits and usage per endpoint0

Sources: Apollo reference pages for People API Search, People Enrichment, Bulk People Enrichment, Organization Search, Organization Enrichment and API Pricing and Credits.

Both search endpoints have a display limit of 50,000 records, which is 100 per page for up to 500 pages, so wide searches need tighter filters (People API Search). Mobile numbers aren't returned inline. When you set reveal_phone_number, Apollo enriches the phone asynchronously and sends it to your webhook_url, or you poll GET /api/v1/webhook_result/{request_id} (People Enrichment).

The workspace endpoints cover creating, updating and searching accounts, contacts, deals and lists; sequences, emails, calls and tasks; conversations; an AI Assistant; and an analytics report endpoint (Apollo docs index). Apollo also ships an MCP server and a CLI on top of the same API.

If you only need enrichment and search, scope a key to those endpoints. See also our post on programmatic CRM enrichment.

How Many Credits Does Each Apollo API Call Use?

Apollo charges credits only when a call returns billable data. A person enrichment costs 1 credit for demographics or email and 8 more for a mobile number, so 1 to 9 per person. Company enrichment is 1. Organization search, job postings and news cost 1 per page. Create, update and list calls cost nothing.

ActionCredit cost
People API Search0
People Enrichment, demographics or email1
People Enrichment, mobile number returned+8 (9 total)
Waterfall email enrichmentTypically 1 to 4; some setups 20+
Waterfall phone enrichmentTypically 8 to 25; some setups 45+
Validate emails and phone numbers (beta)Up to 1 per email; 8 per phone
Organization Enrichment, single or bulk1 per company
Organization Search1 per page (up to 100 results)
Organization Job Postings1 per page (up to 10,000 results)
News Articles Search1 per page (up to 25 results)
Get Complete Person or Organization Info1 per record
Conversations info or export1 per conversation with AI insights, else 0
Create, update, list or manage records0

Source: Apollo docs, API Pricing and Credits, updated October 28, 2026.

There are a few rules in the fine print. Apollo doesn't charge the demographic credit when match_confidence is none. A low match is charged only if it returns data you didn't send. A lookup that finds nothing billable costs 0 credits. Waterfall is the exception: "some vendors consume credits per lookup even when no data is found" (API Pricing and Credits).

<!-- [UNIQUE INSIGHT] -->

The mobile surcharge is where budgets break. Enrich 10,000 people, and say a third come back with a mobile number. That is 10,000 base credits plus about 3,333 × 8 = 26,664 mobile credits, around 36,700 in total. A single Basic seat includes 30,000 credits a year. Model your budget on your expected mobile match rate, not on the 1-credit floor.

To track spend, use Settings > Billing and credits > Credit usage in Apollo, or the view credit usage stats endpoint. Bulk enrichment responses also return credits_consumed, which Apollo says can be a fraction depending on your plan, so parse it as a decimal (Bulk People Enrichment). If you are comparing providers, Datamagnet exposes its balance through a credit balance endpoint.

What Are Apollo's API Rate Limits by Plan?

Apollo sets separate per-minute, per-hour and per-day limits for three groups of endpoints, and they rise by plan. Free allows 50 calls a minute and 600 a day everywhere. Paid plans allow 1,000 enrichment calls a minute with no daily cap, and 50,000 search calls a day. Go over and you get a 429.

PlanGeneral (min / hr / day)Enrichment (min / hr / day)Search (min / hr / day)
Free50 / 200 / 60050 / 200 / 600 (bulk: 20 / 100 / 600)50 / 200 / 600
Basic200 / 400 / 2,0001,000 / no limit / no limit200 / 6,000 / 50,000
Professional200 / 400 / 2,0001,000 / no limit / no limit200 / 6,000 / 50,000
Organization200 / 600 / 6,0001,000 / no limit / no limit200 / 6,000 / 50,000

Source: Apollo docs, Rate Limits, checked November 17, 2026. Enrichment covers people and organization enrichment, bulk variants, job postings and complete person or organization info. Search covers people search, organization search and news search.

Apollo API Daily Rate Limits by Plan Free plan allows 600 requests per day on standard endpoints. Basic and Professional plans allow 2,000 requests per day. Organization plan allows 6,000 requests per day. Source: Apollo.io API documentation, rate limits page, retrieved September 20, 2026. Free 600 Basic 2,000 Professional 2,000 Organization 6,000 Source: Apollo.io API docs, rate limits, retrieved 2026-09-20
Standard-endpoint daily request cap by Apollo plan. Source: Apollo.io rate limits docs, re-checked 2026-11-17.

Three details matter when you build. Limits are per team, shared across every key, user and child workspace. They are per endpoint, with a separate counter for each. And all three windows apply at once, with fixed windows that start at your first request (Rate Limits).

Each response carries headers such as x-minute-requests-left, x-hourly-requests-left and x-24-hour-requests-left. A 429 for your plan's limit has the code USAGE.RATE_LIMIT.API_RATE_LIMIT_EXCEEDED and a retry-after header in seconds. A 429 with USAGE.RATE_LIMIT.PLATFORM_RATE_LIMIT means Apollo-wide load, has no retry-after, and suggests waiting 60 seconds. Build backoff on both from day one. Datamagnet documents its own codes in its API error reference if you are comparing.

Where Does the Apollo API Fall Short for Pipelines?

The main limit is architectural. Apollo enriches by matching your input against its own stored database, so a record is only as current as Apollo's copy. Credits expire every billing cycle, mobile numbers cost 8 credits each and arrive asynchronously, and free-tier limits are too low for a live CRM sync.

Apollo's docs describe enrichment as a match: "If you provide more information about a person, Apollo is more likely to find a match within its database" (People Enrichment). That works well for list building. It is weaker when a pipeline needs someone's title as it stands today.

Other limits developers run into:

  • Mobile reveals cost more and arrive later. The +8-credit surcharge, and 8 to 25 credits for waterfall phone lookups, drive most of the spend. Phones come back by webhook or polling, not in the original response.
  • Credits don't roll over. Unused plan and add-on credits expire at the end of each cycle (Apollo Pricing).
  • Free-tier throttling. 50 calls a minute and 600 a day suit a prototype, not a production sync.
  • Data licensing. Showing Apollo data to people outside your Apollo account needs a custom contract (Developer FAQs).

Stored-database vendors such as Coresignal and People Data Labs share the same trade-off. A job change is the event a stored copy is most likely to miss. Our guide to job-change signals covers how teams detect them.

A data pipeline diagram contrasting a stored database feeding outdated gray profile cards into a CRM against a live request feeding a single fresh blue profile card

Which API Reads Profile Data at the Moment You Call?

Datamagnet does, on request. You send a public profile URL or a company page URL and get structured profile or company data back for 1 credit. With use_cache: "never", the API reads the profile at the moment you call. By default it may return a stored copy, which for companies can be up to 30 days old.

To be direct about the trade-off: Datamagnet has no email or phone lookup and no email verification. If your pipeline needs contact details, that is Apollo's job, and Datamagnet doesn't replace it. Teams use Datamagnet for the profile and company data itself:

You're charged only on successful profile and company requests. New accounts get 10 free credits with no card, and plans are $39 for 1,000 credits, $99 for 10,000 and $199 for 25,000, or pay-as-you-go from $0.02 a credit (Datamagnet pricing). There are no seats.

For a side-by-side on pricing model, freshness and coverage, see Datamagnet vs Apollo. For a worked example, see how a real-time B2B people enrichment pipeline is built, or browse the people API. Datamagnet's quickstart and authentication docs cover key setup and a first request.

Frequently Asked Questions

Is the Apollo API free?

Partly. Every Apollo plan, including Free, includes basic API access, and people search costs 0 credits. Free accounts are limited to 600 calls a day, need a work email for search and enrichment endpoints, and get 900 credits a year. Enrichment spends credits on every plan, so real volume needs a paid seat.

How many credits does the Apollo API use per contact?

A People Enrichment call costs 1 credit for demographics or email, plus 8 more (9 total) if it returns a mobile number. It costs nothing if no billable data is found. Organization Enrichment is 1 credit per company, People API Search is free, and waterfall phone lookups typically cost 8 to 25 credits.

What are Apollo's API rate limits?

Free allows 50 calls a minute and 600 a day on every endpoint group. Paid plans allow 200 general calls a minute, 1,000 enrichment calls a minute with no daily cap, and 50,000 search calls a day. Limits are shared across your team's keys, and exceeding one returns a 429 with a retry-after header.

Where is the API key in Apollo?

Go to Settings > Integrations > API Keys, or open developer.apollo.io/#/keys. Click Create new key, choose endpoints or set it as a master key, then click Create API key and copy it. Only admins, or users with the right permission profile, can create keys. Send the key in the x-api-key header.

Is Apollo's API data live or from a stored database?

From a stored database. Apollo's docs say enrichment tries to "find a match within its database," and searches run against its 240M+ contacts. A record reflects Apollo's latest copy, which can lag a recent job change. Mobile numbers are enriched asynchronously and delivered by webhook or polling after the first response.

Sources

All sources checked November 17, 2026.

Pratik Dani

About Pratik Dani

CEO, Founder