Apollo API
Apollo's People Enrichment endpoint returns a person and the company they work for, and charges Apollo credits that depend on what it finds. A FoxAPIs enrich_person call resolves one person from a name and company and shows the identity check, but returns no company profile. This page lists each Apollo field and what we return for it.
Read 22 November 20263 sources linkedPOST /v1/enrich_personWhere FoxAPIs wins
- You want to see why a match was accepted and which same-name people were set aside.
- You want recent news about the person and links across several places in one call.
- You want a per-call price in dollars that you can read before you buy, from credits that do not expire.
Where Apollo API wins
- You need the company profile in the same call: industry, headcount, revenue, funding, technologies. This call returns the employer's name and not a company profile.
- You need Apollo's seniority, department and function fields, or the contact's city and country.
- You need a mobile number or a personal email revealed by Apollo's own database, or waterfall enrichment across providers.
Who Apollo API is for
Sales and growth teams that use Apollo to find contacts and enrich a person with company details, and want the call to cost nothing when nothing is found.
What Apollo's API says
Apollo is a sales intelligence platform with an API. Facts below are what its documentation and pricing pages showed on 22 November 2026.
- People Enrichment is POST https://api.apollo.io/api/v1/people/match, with the key in an x-api-key header. It enriches one person; a separate bulk call takes up to ten. Apollo People Enrichment referenceread 22 November 2026
- Credits: between 1 and 9 Apollo credits per person without waterfall enrichment, charged only if credit-consuming data is found: 1 Apollo credit for demographics or email, plus 8 more if a mobile phone is returned. If nothing credit-consuming is found, the request uses none. Apollo People Enrichment referenceread 22 November 2026
- Apollo's pricing page names four plans (Free, Basic, Professional, Custom), says credits are pooled across the team, granted each billing cycle and do not roll over, and shows no dollar prices. Apollo pricing pageread 22 November 2026
- Apollo's own insights article lists, per user per month on annual billing: Free $0, Basic $49, Professional $79, Organization $119 with a 3-user minimum. It does not state credits per plan or the price of extra credits. Apollo plan articleread 22 November 2026
| Plan | Listed price | Includes |
|---|---|---|
| Free | Free | Not stated on the pages we read |
| Basic | $49 per user per month, annual billing | Credits not stated on the pages we read |
| Professional | $79 per user per month, annual billing | Credits not stated on the pages we read |
| Organization | $119 per user per month, annual billing, 3-user minimum | Credits not stated on the pages we read |
Read on 22 November 2026 from Apollo API's page. We state only what the pages we link showed that day.
How the two differ
Apollo's endpoint returns a stored contact record together with the company it belongs to, priced in Apollo credits that vary with what is found. A FoxAPIs call looks one person up live, confirms what it can and returns the identity check, with a fixed number of credits per call. Apollo returns much more about the company; we return more about whether the match is right.
Field by field: Apollo's documented response against ours
We lose rows here. 27 of the 42 Apollo API fields have no field of ours. Where a row says we do not return it, we do not.
Apollo lists the person object and a nested organization object. Every field below is as its reference lists it.
| Apollo field | Ours | What we return (real sample, 19 November 2026) |
|---|---|---|
| person.id | We do not return it | We return no Apollo-style id. |
| person.first_name | Closest field | full_name: One field for the whole name; we do not split it. |
| person.last_name | Closest field | full_name: One field for the whole name; we do not split it. |
| person.name | We return it | full_name: Same data, our field name. |
| person.linkedin_url | We return it | linkedin_url: Same data, our field name. |
| person.title | We return it | title: Same data, our field name. |
| person.email | Closest field | emails: Candidates, each labelled by how we came by it; none in the sample was confirmed by delivery. |
| person.email_status | Closest field | emails: Each address carries a status such as derived or guess, and a note on how it was found. We do not report verified or unavailable. |
| person.extrapolated_email_confidence | Closest field | emails: A status per address, not a number. |
| person.photo_url | We return it | photo_url: Same data, our field name. |
| person.twitter_url | We return it | twitter_url: Same data, our field name. |
| person.github_url | We return it | github_url: Same data, our field name. |
| person.facebook_url | We do not return it | We do not return this. |
| person.headline | We do not return it | We do not return this. |
| person.match_confidence | Closest field | overall_confidence: A 0 to 1 score, with identity_verification giving the reasons. |
| person.employment_history | Closest field | employment_history: Title, company and dates for each job; no job description. |
| person.city | We do not return it | We do not return a location. |
| person.state | We do not return it | We do not return this. |
| person.country | We do not return it | We do not return this. |
| person.seniority | We do not return it | We do not return this. |
| person.departments | We do not return it | We do not return this. |
| person.subdepartments | We do not return it | We do not return this. |
| person.functions | We do not return it | We do not return this. |
| person.contact_id | We do not return it | We do not return this. |
| person.is_likely_to_engage | We do not return it | We do not return this. |
| person.show_intent | We do not return it | We do not return this. |
| organization.name | Closest field | employer: The employer's name only. |
| organization.website_url | We do not return it | We do not return this. |
| organization.primary_domain | We do not return it | We do not return this. |
| organization.logo_url | We do not return it | We do not return this. |
| organization.industry | We do not return it | We do not return this. |
| organization.estimated_num_employees | We do not return it | We do not return this. |
| organization.annual_revenue | We do not return it | We do not return this. |
| organization.total_funding | We do not return it | We do not return this. |
| organization.latest_funding_stage | We do not return it | We do not return this. |
| organization.funding_events | We do not return it | We do not return this. |
| organization.technology_names | We do not return it | We do not return this. |
| organization.founded_year | We do not return it | We do not return this. |
| organization.raw_address | We do not return it | We do not return this. |
| organization.naics_codes | We do not return it | We do not return this. |
| organization.short_description | We do not return it | We do not return this. |
| phone_enrichment | Closest field | phones: A list of numbers; no mobile reveal and no labels. |
Ours only: identity_verification (why the match was accepted), possibly_someone_else (same-name people set aside), news_mentions, education, and links to places Apollo does not list such as crunchbase_url.
Source for the Apollo API column: Apollo People Enrichment reference, read 22 November 2026.
What a FoxAPIs call returns
POST /v1/enrich_person
Give it a name and a company. It resolves the person and returns confirmed profile links, employment and education history, email candidates each labelled by how we came by them, phone numbers, recent news about the person, and an identity check that says why the match was accepted and which same-name people were set aside. Costs 100 credits a call.
| Field | Real example (19 November 2026) |
|---|---|
| full_name | Patrick Collison |
| employer | Stripe |
| title | none |
| overall_confidence | 0.45 |
| linkedin_url | (text, not shown here) |
| twitter_url | none |
| github_url | none |
| photo_url | none |
| emails | a list of 5 |
| phones | none |
| employment_history | a list of 2 |
| education | a list of 3 |
| news_mentions | a list of 8 |
| identity_verification | an object with 16 fields |
| possibly_someone_else | a list of 4 |
curl -X POST https://api.foxapis.com/v1/enrich_person \
-H "Authorization: Bearer YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{"name":"Satya Nadella","company":"Microsoft"}'Price at the costliest listed tier
| Apollo API or FoxAPIs | Price |
|---|---|
| Costliest call | Up to 9 Apollo credits for one person (1 for demographics or email, plus 8 if a mobile phone is returned). Apollo's pages do not state a price for a credit or how many credits each plan holds, so we show no dollar figure for it. source |
| FoxAPIs /v1/enrich_person | $0.980 a call: 100 credits a call times the price per credit on the Builder plan, calculated by us. The welcome credits cover about 10 calls, no card. |
Dollar figures for FoxAPIs are computed from plans.json when this page is built; none is typed. We show a dollar figure for Apollo API only where its own pages gave the numbers.
Start with 1,000 credits
Start with 1,000 credits, no card. They arrive once you confirm your email and expire 90 days after they are added; credits you buy never expire. Then from $10. Type your email and the key appears on this page, once, with the request below filled in.
By continuing you agree to the Terms and the Privacy page.
Key created. It is shown once: copy it now.
Move one call
Before: Apollo request, from its reference page
curl -X POST "https://api.apollo.io/api/v1/people/match?name=Satya%20Nadella&organization_name=Microsoft" \ -H "x-api-key: YOUR_APOLLO_KEY"
After: the same job on FoxAPIs. Replace YOUR_KEY with the key from the box above.
curl -X POST https://api.foxapis.com/v1/enrich_person \
-H "Authorization: Bearer YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{"name":"Satya Nadella","company":"Microsoft"}'Apollo sends its inputs as query parameters; ours is a JSON body with name and company.
Questions before you switch
Does a FoxAPIs call cost nothing when nothing is found?
We have not shown that on this page. Apollo's reference says a request uses no credits if no credit-consuming data is found. For ours, read the pricing page before you rely on a no-match being free.
Can I get a mobile number?
A phones field comes back when numbers could be found, without a label saying whether one is mobile. Apollo's reveal_phone_number option returns mobile numbers from its own database.
Where is the company data?
It is not returned. The organization rows above are marked as not returned. Use Apollo, or call a company endpoint separately.
Are the emails verified?
No. They are candidates, each labelled by how we came by them. None in our sample was confirmed by delivery.
When to stay with Apollo API
- You need the company profile in the same call: industry, headcount, revenue, funding, technologies. This call returns the employer's name and not a company profile.
- You need Apollo's seniority, department and function fields, or the contact's city and country.
- You need a mobile number or a personal email revealed by Apollo's own database, or waterfall enrichment across providers.
- You already work inside Apollo's sequences and contact lists: the record there is what you act on.
When a FoxAPIs call is the better fit
- You want to see why a match was accepted and which same-name people were set aside.
- You want recent news about the person and links across several places in one call.
- You want a per-call price in dollars that you can read before you buy, from credits that do not expire.