ZoomInfo API
ZoomInfo's Enrich API takes up to 25 contacts or companies in one request and returns the fields you list, one credit per record the first time in 12 months. A FoxAPIs enrich_person call resolves one person from a name and company and shows how sure the match is, but returns no company fields such as revenue or headcount. This page lists the ZoomInfo fields we compared and what we return for each.
Read 23 November 20266 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 profile links in the same call.
- You want a published per-call price in dollars before you sign anything, from credits that do not expire when you buy them.
Where ZoomInfo API wins
- You enrich companies and need firmographic fields: revenue, employee count, industry codes, funding amounts, parent company. We have no company enrichment call that returns them.
- You enrich in bulk: ZoomInfo takes up to 25 records a request. enrich_person takes one person a call.
- You need management level, job function, a direct or mobile phone from ZoomInfo's own database, or its contact accuracy score.
Who ZoomInfo API is for
Sales and marketing operations teams that enrich contacts and companies in bulk with firmographics, job function and management level, and already hold a ZoomInfo contract.
What ZoomInfo's API docs say
ZoomInfo is a sales intelligence platform. Facts below are what its API documentation showed on 23 November 2026.
- docs.zoominfo.com answers with a 301 redirect to docs.gtm.ai, where the Data API V1 reference now lives. ZoomInfo developer docsread 23 November 2026
- Enrich Contacts retrieves information about up to 25 contact records in one request; Enrich Companies does the same for up to 25 company records. ZoomInfo API docs homeread 23 November 2026
- Each record returned by Enrich is charged one credit, unless the record is already under management. If no match is found or an error is returned, no credit is charged. ZoomInfo: Enrich Contacts referenceread 23 November 2026
- A record enriched for the first time within a rolling 12-month period consumes one credit and is then under management for a year. ZoomInfo: credit usage and limitsread 23 November 2026
- The credit page gives no dollar amounts. It says customers purchase credits in bulk on an annual basis. ZoomInfo: credit usage and limitsread 23 November 2026
- Default rate limit is 25 requests per second per tenant; the Premium and Premium+ add-ons raise it to 30 and 35. ZoomInfo: credit usage and limitsread 23 November 2026
- The contact output fields include managementLevel, jobFunction, jobTitle, email, mobilePhone, education, employmentHistory, techSkills, yearsOfExperience and contactAccuracyScore. ZoomInfo: Enrich Contacts referenceread 23 November 2026
- The company output fields include revenue, employeeCount, industries, naicsCodes, sicCodes, totalFundingAmount, recentFundingDate, parentName and ticker. ZoomInfo: Enrich Companies referenceread 23 November 2026
Read on 23 November 2026 from ZoomInfo API's page. We state only what the pages we link showed that day.
How the two differ
ZoomInfo's Enrich returns stored contact and company records, 25 at a time, charged by contract. A FoxAPIs enrich_person call looks up one person live and returns the identity check with it. ZoomInfo returns far more about the company and the contact's role; we return more about whether the match is right.
Field by field: ZoomInfo's Enrich output fields against ours
We lose rows here. 10 of the 20 ZoomInfo API fields have no field of ours. Where a row says we do not return it, we do not.
Contact rows come from ZoomInfo's Enrich Contacts output field list; rows starting company come from its Enrich Companies list. ZoomInfo lists more than 100 fields in all; we compare the main groups.
| ZoomInfo field | Ours | What we return (real sample, 19 November 2026) |
|---|---|---|
| firstName, lastName, middleName | Closest field | full_name: One field for the whole name; we do not split it. |
| jobTitle | We return it | title: Same data, our field name. |
| companyName | Closest field | employer: The employer's name only. |
| email, emailAlt, supplementalEmail | Closest field | emails: Candidates, each with a status and a note on how it was found. |
| mobilePhone, phone, directPhoneAlt | Closest field | phones: A list of numbers when we find one, each with a source link; no direct-or-mobile split. |
| education | We return it | education: Same data, our field name. |
| employmentHistory | We return it | employment_history: Title, company and dates for each job. |
| picture | We return it | photo_url: Same data, our field name. |
| externalUrls | Closest field | linkedin_url: Separate fields for LinkedIn, Twitter, GitHub and other profile links. |
| contactAccuracyScore | Closest field | overall_confidence: A 0 to 1 score, with identity_verification giving the reasons. |
| managementLevel, jobFunction | We do not return it | We do not return this. |
| yearsOfExperience, techSkills | We do not return it | We do not return this. |
| city, state, country, metroArea | We do not return it | We do not return a location. |
| company: revenue, revenueRange | We do not return it | We do not return this. |
| company: employeeCount, employeeRange, employeeGrowth | We do not return it | We do not return this. |
| company: industries, naicsCodes, sicCodes | We do not return it | We do not return this. |
| company: totalFundingAmount, recentFundingAmount, recentFundingDate | We do not return it | get_company_report writes funding as text in a report; it returns no amount fields. |
| company: parentName, ultimateParentName | We do not return it | We do not return this. |
| company: website, domainList, logo | We do not return it | We do not return this. |
| company: competitors, products | We do not return it | We do not return this. |
Ours only: github_url and other profile links, news_mentions, identity_verification (why the match was accepted), possibly_someone_else (same-name people set aside) and deeper_dossier.
Source for the ZoomInfo API column: ZoomInfo: Enrich Contacts reference · ZoomInfo: Enrich Companies reference, read 23 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) |
| 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"}'POST /v1/get_company_report
The closest call we have on the company side, and a different job: a written, sourced report on one company for one decision. It returns no firmographic fields such as revenue, headcount or industry codes. Costs 200 credits a call.
| Field | Real example (23 November 2026) |
|---|---|
| sections | a list of 21 |
| headline | Buying the whole company |
| quality_flags | a list of 20 |
curl -X POST https://api.foxapis.com/v1/get_company_report \
-H "Authorization: Bearer YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{"name":"Duolingo","angle":"selling_to"}'Price at the costliest listed tier
| ZoomInfo API or FoxAPIs | Price |
|---|---|
| ZoomInfo Enrich API | One credit per record enriched for the first time in 12 months; no match, no charge. The docs give no dollar figure and say credits are bought in bulk on an annual basis, so we show none. source |
| ZoomInfo pricing page | We could not read their pricing page on 23 November 2026: the server answered 403 Forbidden, and its API product pages answered 403 as well. We show no plan or price from them. 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. |
ZoomInfo's price per credit is not public on the pages we could read, so no per-record comparison is made.
Dollar figures for FoxAPIs are computed from plans.json when this page is built; none is typed. We show a dollar figure for ZoomInfo 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: We could not read ZoomInfo's request examples, so we show no ZoomInfo request. Keep the person's name and company from your current lookup and send them as below.
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"}'The input is a name and a company, one person a call. ZoomInfo accepts up to 25 records a request, so a batch needs one call per person.
Questions before you switch
Is ZoomInfo's API price public?
Not on the pages we could read on 23 November 2026. The API docs give credits per record and no dollar amount, and the pricing page answered 403.
Can enrich_person return company revenue or headcount?
No. It returns the employer's name and the person's record; no firmographic fields.
Do you have company enrichment?
Not as fields. get_company_report writes a sourced report on one company for one decision; it is not a firmographics call.
Can I send 25 people in one request?
No. enrich_person takes one person a call.
When to stay with ZoomInfo API
- You enrich companies and need firmographic fields: revenue, employee count, industry codes, funding amounts, parent company. We have no company enrichment call that returns them.
- You enrich in bulk: ZoomInfo takes up to 25 records a request. enrich_person takes one person a call.
- You need management level, job function, a direct or mobile phone from ZoomInfo's own database, or its contact accuracy score.
- You already work in ZoomInfo's platform and want the data where your team acts on it.
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 profile links in the same call.
- You want a published per-call price in dollars before you sign anything, from credits that do not expire when you buy them.