ZoomInfo API: Access, Pricing, Limits and Alternatives (2026)

Learn how the ZoomInfo API works in 2026, including access, OAuth, endpoints, credits, rate limits, pricing and the best alternatives.

Marharyta Sevostianenko Marharyta Sevostianenko SDR/SAAS & B2B sales Updated 24 min read
Go Back

TL;DR: The ZoomInfo API gives licensed customers programmatic access to ZoomInfo company, contact, enrichment, intent and audience data. In 2026, new integrations use the GTM API documented at docs.gtm.ai, which authenticates with OAuth 2.0 (Authorization Code with PKCE or Client Credentials). The older JWT workflow belongs to the Legacy Enterprise API, which ZoomInfo says is being deprecated. Search is free, each new enriched record costs one data credit, and rate limits run from 5 to 35 requests per second by package. ZoomInfo now lists a free self-serve tier on gtm.ai/pricing, while Enterprise packages remain custom-priced, so confirm the package, credit model, endpoint coverage and limits before you build.

This guide covers access, authentication, endpoint families, returned data, credits, pricing and limits first. Alternatives (Apollo, Cognism, Clay, Lusha, People Data Labs and Generect) come after that, for teams deciding whether ZoomInfo is the right API at all.

ZoomInfo API questionShort answer (checked 2026-10-26)Source
Who can use it?Customers with a GTM.ai or Enterprise license with API access; Enterprise customers create apps in the Developer PortalStandard App docs
Authentication (new platform)OAuth 2.0: Authorization Code with PKCE for user-based apps, Client Credentials for server-to-serverAuthentication docs
Authentication (legacy)JWT from a client ID plus private key or from a username and password; token valid for one hourLegacy Enterprise API docs
Base URL (new platform)api.zoominfo.com/gtmPagination docs
Rate limitsBuilder 5 req/s, Standard 25 req/s, Scaling 35 req/s, plus hourly and daily capsRate limits docs
CreditsSearch and lookup are free; 1 data credit per new enriched company or contact record, then free re-enrichment for 12 monthsCredit usage docs
PricingFree tier with 1,000 data and 1,000 AI credits, top-ups from $20; Enterprise is customGTM AI pricing

What Is the ZoomInfo API?

The ZoomInfo API is programmatic access to ZoomInfo’s B2B company and contact data. Instead of logging into the ZoomInfo UI to export CSV files, you call the API from your CRM sync, data pipeline, product or AI agent. ZoomInfo’s own overview describes it as a way to “search companies and contacts, enrich records, build audiences, and power AI agents”.

On the current platform, the documentation groups the API into four areas:

  1. Data API: search and enrich companies and contacts using firmographic and technographic filters, retrieve email addresses, contact numbers and org-chart data, and search or enrich intent signals, news and scoops.
  2. Audience API: build and manage lists for activation across your GTM stack.
  3. Agents API: run and monitor Agent Teams and subscribe to webhooks and events for async job completion.
  4. Context API: store buyer personas, ICPs, competitors and products, then use them to find similar companies and recommended contacts.

Responses are JSON (the examples use the JSON:API media type application/vnd.api+json). Typical uses are real-time enrichment of new sign-ups, scheduled refreshes of CRM records and event-triggered enrichment from product activity. ZoomInfo also documents an MCP server and a CLI on the same platform for agent workflows.

ZoomInfo API Families: What You Actually Get

The endpoint families you can call depend on whether you are on the new GTM API or still on the Legacy Enterprise API, and on the SKUs in your contract. Intent endpoints, for example, require the Intent SKU.

1. Search API

Search Contacts and Search Companies accept filter criteria and return matching records with IDs and summary fields, so you can rank candidates before you spend credits. Search is free on the new platform. Results are paginated with page[number] and page[size], with a maximum page size of 100. Search Intent, Search News and Search Scoops cover signal data.

2. Enrich API

This is where credits get consumed. Enrich Contacts and Enrich Companies return full profiles for up to 25 records per call, and further Enrich endpoints cover corporate hierarchy, intent, news, org charts, scoops, technologies and hashtags. You match on ZoomInfo IDs or on inputs such as company name, website or contact details, and you choose the output fields you need.

3. Bulk API

The Legacy Enterprise API includes Bulk endpoints for search and redeem jobs on contacts and companies; ZoomInfo’s legacy getting-started guide says Bulk Search allows up to 200,000 results per search query. On the new platform, ZoomInfo’s bulk guidance is to page through search results and batch enrichment in groups of 25 within your rate limits.

4. WebSights API

WebSights identifies anonymous website traffic at company level and links it to ZoomInfo profiles. It is documented as a separate family in the Legacy Enterprise API, with its own record and request limits returned in response headers. Check with ZoomInfo whether your package includes it before you design an ABM workflow around it.

5. Compliance API

The Compliance API in the Legacy Enterprise API covers data-privacy compliance for contacts stored in the ZoomInfo database. It matters when you run outbound at scale and need to honour opt-outs and removal requests in your own systems.

Authentication and the 2026 API Platform Update

If you are building a new integration in 2026, build on the new platform. The Legacy Enterprise API documentation states that the legacy API “is currently in the process of being deprecated” and that all new development should use the new API. The notice we checked gives no shutdown date. The documentation for the new API now lives at docs.gtm.ai; old docs.zoominfo.com links redirect there.

ZoomInfo API 2026 comparison: new GTM API vs Legacy Enterprise API by auth, docs, rate limits, usage and API families
One API has OAuth 2.0 and a future; the other has a one-hour JWT and no published retirement date.

New platform: OAuth 2.0. ZoomInfo’s authentication docs say the new platform uses OAuth 2.0 to authenticate every API request. You create a Standard App (or a Partner App if you are a ZoomInfo partner), receive a client ID and client secret, choose scopes and then pick a flow:

Use caseOAuth 2.0 flow
Your app calls ZoomInfo on behalf of a signed-in userAuthorization Code Flow (PKCE), with refresh tokens
Backend services, scheduled jobs and data syncs with no user loginClient Credentials Flow
Partner application used by customer organisationsAuthorization Code Flow (PKCE)
  1. Enterprise customers sign in to the ZoomInfo Developer Portal and select Create App; GTM.ai self-serve customers create the app from the Developer tab in GTM.ai.
  2. Enter the app details, choose Authorization Code (PKCE) or Client Credentials, add redirect URLs for the user-based flow and select only the OAuth scopes you need.
  3. Store the client ID and client secret server-side. Never ship them in client-side code.
  4. Request an access token with your flow and send it as Authorization: Bearer <token> on every request. ZoomInfo’s Test API Access page generates a token for a first test call.

Legacy Enterprise API: JWT. The legacy API authenticates differently. Its documentation and getting-started guide describe two methods, PKI (a client ID plus private key, used with ZoomInfo’s auth libraries for Java, Python and NodeJS) or username and password. Both return a JSON Web Token that is valid for one hour. The key-pair method is the one ZoomInfo recommends for production on the legacy API. Treat this as a migration topic, not as the default for a 2026 build.

Why it matters for a contract: if your current integration runs on the legacy API, plan the move to OAuth 2.0 and the new endpoints during the contract term, and include that engineering effort in your total cost.

Rate Limits and Throughput (2026 Numbers)

On the new platform, every request is checked against three windows at once: per second, a rolling hour and a rolling day. ZoomInfo’s rate limits page (updated October 2026) lists these packages:

PackagePer secondPer hourPer day
Builder5 req/s10,800129,600
Standard25 req/s54,000648,000
Scaling35 req/s75,600907,200

The hourly cap is what most teams hit first. On Standard, 25 requests per second could in theory reach 90,000 requests an hour, but the hourly window stops you at 54,000. Limits count requests, not records: Search returns up to 25 records per request through the API and up to 10 through MCP or the CLI, and Enrich takes up to 25 records per call. A rejected request returns 429 with Retry-After and X-RateLimit-Rejected-Bucket (second, hour or day), and rejected requests do not consume quota.

Two caveats from the docs themselves. The credit usage page lists the tiers as Default 25, Premium 30 and Premium+ 35 requests per second and says rate-limit headers are not currently returned, while the rate limits page documents X-RateLimit-* headers on every response. Build your client so it works either way: read the headers when they are present and fall back to exponential backoff with jitter.

The Legacy Enterprise API uses an older scheme. Its documentation lists 1 request per second for the authentication endpoint, 25 requests per second (1,500 per minute) for the Standard APIs, WebSights API and Compliance API, and 33 requests per second (2,000 per minute) for the Scaling APIs.

Legacy Enterprise API typeRate limitPer minute
Authentication endpoint1 req/second60
Standard APIs, WebSights API, Compliance API25 req/second1,500
Scaling APIs (Webhooks, Bulk)33 req/second2,000

Two other limits matter more than rate limits in practice:

  • Request limits: total API calls allowed in your contract term
  • Record limits: total records you can retrieve; on the new platform each enrichment counts against the record limit even when a record under management costs no new credit

These are set contractually and are the main usage constraint for most teams. Running out of records before the contract year ends is a real risk for teams that underforecast usage during procurement. The Usage Data endpoint returns your current API usage and limits, so monitor it from day one.

What Does the ZoomInfo API Actually Return?

When an Enrich call matches a record, you get structured JSON with the output fields you requested. Field availability depends on your package. The documented families include:

  • Contact fields: email addresses, direct and mobile phone numbers, job title, department, seniority, location and do-not-call flags
  • Company fields: website, revenue, employee range and growth, industry, location count, founded year and social profiles
  • Hierarchy data: parent company, subsidiaries and org charts
  • Technographic data: technologies ZoomInfo has identified at the company
  • Signals: intent topics (Intent SKU required), news and scoops
  • Quality metadata: a contact accuracy score, last-updated and valid dates, and a match status such as FULL_MATCH on enrich responses

Use the quality metadata. A match status and an accuracy score let you route uncertain matches to review instead of writing them straight into your CRM.

ZoomInfo API Pricing in 2026: Free Tier, Credits and Enterprise Contracts

ZoomInfo now publishes self-serve pricing for API access on GTM AI, but not for Enterprise contracts. As listed on 2026-10-26:

PlanWhat ZoomInfo lists
Free (self-serve)$0 to start, 1,000 data credits and 1,000 AI credits, no credit card; MCP, API and CLI access; 5 req/s and 5 apps; free search, lookup and find similar
Pay as you goTop-up packs from $20, no seat fees; ZoomInfo’s own example prices enriching 500 CRM leads at 500 data credits, $215
EnterpriseCustom pricing with annual credit volume, Records Under Management, SSO/SAML, custom rate limits and SLA-backed support; mobile phone data is listed among Enterprise package inclusions

The credit rules are documented on the credit usage page: Lookup, Search Companies, Search Contacts and the find-similar and recommended-contact endpoints are free; Enrich Companies and Enrich Contacts cost 1 bulk data credit per new record; account and contact research use AI credits. Once a record is enriched it is under management for 12 months, so re-enriching it in that window does not consume another credit, although it still counts against your record limit.

Enterprise SalesOS and API contracts are still quoted by sales. Vendr’s ZoomInfo pricing guide says pricing depends on seats, platforms, data credits, contract length and add-ons, and notes that buyers often get below-list pricing with multi-year terms or higher seat volumes.

Watch out for:

  • Auto-renewal clauses: Vendr reports notice periods of typically 30–90 days and suggests negotiating 90–120
  • Annual price increases: Vendr reports escalation clauses of typically 5–10% a year; negotiate a cap
  • Unused credits: Enterprise credits are bought as annual volume, so an overestimate is wasted budget
  • Add-on costs: intent data, mobile phone data and some AI features are tied to specific SKUs or packages

What are the best alternatives to ZoomInfo?

The strongest ZoomInfo alternatives are Apollo for an all-in-one database and outreach workflow, Cognism for EMEA-focused phone prospecting, Clay for multi-provider enrichment, Lusha for rep-led contact lookup, People Data Labs for developer-led data pipelines, and Generect for API-first lead search, enrichment and verified work-email discovery. None is a universal replacement: shortlist by the ZoomInfo capability you actually use.

AlternativeBest fit to testBuying modelKey boundary to validate
ApolloDatabase plus sequencing in one productSubscription and creditsCoverage and verified-contact yield for your ICP
CognismEMEA phone-first workflowsSales-led contractCountry-level mobile coverage and contract fit
ClayCustom enrichment waterfallsUsage-based creditsSetup effort, provider spend and workflow latency
LushaFast rep-led email and phone lookupFree and paid tiersDepth and credits per usable contact
People Data LabsCustom applications and data pipelinesUsage-based API plansEngineering effort and required-field coverage
GenerectAPI-first search, enrichment, email finding and validationPay as you go: free search; API real-time search and enrich $0.04 per returned result, $0.02 per valid email foundMatch rate and latency; no intent or conversation-intelligence suite
ZoomInfo alternatives decision matrix comparing Apollo, Cognism, Lusha, Clay, People Data Labs, and Generect by buyer job
Choose a ZoomInfo alternative by the job: rep-led prospecting, builder-led data workflows or API-first verified work-email discovery.

Generect’s public migration guide covers teams moving from ZoomInfo, Apollo or Hunter, while its API reference exposes separate real-time lead search, enrichment and verified work-email finder endpoints. That makes it comparable on observable workflow coverage; it does not imply parity with ZoomInfo’s intent or conversation-intelligence products.

Before replacing ZoomInfo, test 200 representative records and calculate valid emails, working direct dials, correct titles and companies, missing required fields, workflow time and cost per usable record. Compare with our guides to B2B data providers, data enrichment APIs and email finder APIs.

Data Accuracy: What Published Benchmarks Show

Vendor accuracy claims are not comparable to each other, so look for tests that run several providers on the same records. The most cited 2026 test is Cleanlist’s comparison of Apollo and ZoomInfo on the same 1,000 B2B leads. Cleanlist sells a competing waterfall enrichment product, so read it as a vendor-run test, not an independent audit.

Metric (Cleanlist, 1,000 leads)ZoomInfoApolloGenerect
Email match rate84%78%98% valid emails (published product claim, not part of this test)
Mobile phone match rate67%41%98% phone accuracy (published product claim, not part of this test)
Direct dial match rate71%52%N/A
Job title accuracy (sample of 200)92%89%N/A

In that test ZoomInfo’s clearest advantage is phone data: a 67% mobile match rate against Apollo’s 41% matters if cold calling is your main channel. The email gap is smaller. A match rate is not the same as deliverability, so verify emails before high-volume sending whichever provider you use.

The same Cleanlist article argues that single-database providers rarely clear about 85% email accuracy because contact data changes faster than any one database refreshes. That is the author’s interpretation of its results, not a measured ceiling. Your own 200-record test on your ICP is the number to trust.

New in 2026: GTM.AI, MCP and CLI Access

The biggest 2026 change is where and how you build. The API documentation moved to GTM.AI, and the same platform documents three ways in:

ZoomInfo MCP and CLI for AI agents

ZoomInfo documents an MCP server and a CLI alongside the REST API, and the free tier includes all three. Through MCP and the CLI, Search returns up to 10 records per request instead of 25, which lowers record throughput at the same request rate. If you are wiring ZoomInfo into an AI agent, compare MCP convenience with direct API throughput before you choose.

Agents, Audiences and Context APIs

Beyond search and enrich, the new platform adds APIs for audiences, Agent Teams with webhooks and events, and stored context such as ICPs, buyer personas, competitors and products, which feed company lookalikes and contact recommendations. These are useful if you want ZoomInfo to run more of the workflow; they are optional if you only need enrichment.

ZoomInfo API vs Alternatives: 2026 Head-to-Head Comparison

Here is how ZoomInfo’s API compares with the main alternatives on access, pricing model and what has actually been measured. We only list accuracy numbers that come from a named test.

ProviderAPI accessPricing modelPublished accuracy evidenceArchitecture
ZoomInfo APIOAuth 2.0 apps; free self-serve tier and EnterpriseData and AI credits; Enterprise custom84% email, 67% mobile match (Cleanlist, 1,000 leads)Single database
Apollo APIREST APIPer-seat plans with credits78% email, 41% mobile match (Cleanlist, 1,000 leads)Single database
Clearbit (HubSpot)Inside HubSpot as Breeze IntelligenceHubSpot creditsNo shared test foundSingle database
People Data LabsDeveloper APIUsage-based API plansNo shared test foundSingle database
ClayWorkflow tool with HTTP and provider integrationsUsage-based creditsDepends on the providers in your waterfallMulti-provider waterfall
GenerectLive API and MCP, pay as you goFree search; $0.04 per real-time search or enrich result, $0.02 per valid email found. See live pricing98% valid emails (published product claim)Real-time search and verification

Apollo ($49–$119/user/month)

Apollo is the most common ZoomInfo alternative for mid-market and SMB teams. It publishes per-seat pricing (Basic $49, Professional $79 and Organization $119 per user per month on annual billing, as read by Cleanlist in September 2026), and bundles sequences and a dialer. In Cleanlist’s test the email gap to ZoomInfo was small (78% against 84%), while the mobile gap was large (41% against 67%). Model credit usage, because the credit meter, not the seat price, drives real cost.

Clearbit by HubSpot

Best fit if you already run HubSpot. Clearbit’s enrichment now lives inside HubSpot as Breeze Intelligence, so it is tightly coupled to HubSpot licensing and credits and is not a standalone enrichment API for other stacks. See our HubSpot data enrichment guide for how it compares inside the CRM.

People Data Labs

Developer-first raw data with usage-based API pricing and no seat model. Best for data teams building custom enrichment pipelines who want flexible access without an enterprise sales cycle. Test required-field coverage on your ICP, because a large record count does not tell you how many records have the fields you need.

Waterfall Enrichment (Cleanlist, Clay)

The architectural alternative to single-database providers: query several providers in order, stop at the first verified result and verify email deliverability before returning it. Cleanlist reports 98% verified work emails and 85% phone numbers on its own 500-lead benchmark, which is a vendor claim about its own product. The trade-offs are setup effort, latency from sequential lookups and no native intent or conversation intelligence.

Single-Database vs Waterfall: Why Architecture Matters

This is one of the most useful concepts for evaluating ZoomInfo in 2026, and one many buyers skip.

Single-database providers (ZoomInfo, Apollo, Clearbit) maintain a proprietary database and return the stored record when you call the API. Latency is low and the schema is consistent. Accuracy depends on how recently that record was verified, which is why ZoomInfo exposes last-updated dates and an accuracy score on each contact.

Waterfall providers query several sources per lookup, then verify email deliverability before returning a result. Coverage can be higher on hard segments, but each lookup takes longer, costs vary by which provider answered and field formats are less uniform.

The trade-off is scope. Waterfall and real-time tools do not bundle intent signals, conversation intelligence or a full GTM suite. If you need ZoomInfo’s full stack (enrichment, intent, WebSights and AI workflows), there is no like-for-like waterfall replacement. If you mainly need accurate contact data at scale, test both architectures on the same records.

When ZoomInfo API Is the Right Choice

ZoomInfo makes sense when:

  • Cold calling is core to your motion. In Cleanlist’s 1,000-lead test, ZoomInfo matched 67% of mobile numbers against Apollo’s 41%. For a high-volume dialing team that gap compounds across thousands of calls.
  • Intent data changes your targeting. ZoomInfo sells intent signals with the Intent SKU and exposes them through Search Intent and Enrich Intent, next to the contact data. If timing outreach around research activity is central to your strategy, that bundle is a real differentiator.
  • You want to consolidate your GTM stack. Enrichment, intent, audiences, agents and webhooks on one platform reduce the number of vendors and integrations to manage.
  • Compliance is a high-stakes requirement. ZoomInfo documents compliance endpoints and do-not-call flags. For companies under heavy regulatory scrutiny, an established vendor’s governance process can reduce risk; review it with your legal team.
  • Budget allows. The free tier is fine for testing, but production volume, mobile data and custom limits sit in Enterprise packages that are quoted by sales.

When ZoomInfo API Is Overkill

ZoomInfo is the wrong choice when:

  • Your motion is primarily email. If you do not need direct dials or intent, compare the cost per valid email across providers on your own records before paying for phone and signal coverage you will not use.
  • You need predictable spend at small volume. The self-serve tier helps, but Enterprise contracts are annual. If you want to trial, iterate and scale gradually, compare pay-as-you-go providers too.
  • Email deliverability is paramount. An 84% match rate still leaves records to verify. If you send high-volume automated email, add a validation step or use a provider that verifies at lookup time.
  • You target SMB or non-US markets heavily. Coverage differs by segment and country for every provider. Test those segments specifically before committing.

CRM Integration and Workflow Patterns

ZoomInfo offers native CRM integrations, which cover the most common enrichment workflows without custom code. Teams building custom pipelines should follow the pattern ZoomInfo’s own docs recommend:

  1. Search to identify: run a narrow Search Companies or Search Contacts query (free) and page through only the results you need
  2. Match and rank: apply your own match logic (or human review for ambiguous matches) before you spend credits
  3. Enrich to retrieve: call Enrich for the selected records, up to 25 per call (this is where credits are consumed)
  4. Write to CRM: map ZoomInfo fields to your CRM schema, and keep the match status and accuracy score
  5. Schedule refresh: cache enriched IDs and re-enrich inside the 12-month Records Under Management window, when it costs no new credit

For large backfills on the new platform, spread batched enrich calls across the hour and day so you stay under the hourly cap. Legacy contracts can still use the Bulk endpoints for asynchronous jobs. For real-time enrichment, such as enriching a sign-up the moment a form is submitted, the synchronous Enrich endpoint with caching handles most cases within the rate limits.

The Generect Alternative: Live Data vs Static Database

At Generect, we take a different approach to data freshness. Instead of returning a stored record from a periodically refreshed database, the Generect Live API fetches B2B data in real time from sources such as LinkedIn and Crunchbase and finds and validates work emails on demand. What that means in practice:

The trade-off: we do not have ZoomInfo’s intent signals or conversation intelligence. If those features are core to your motion, ZoomInfo’s integrated platform is genuinely differentiated.

For teams mainly running email-based outbound or building enrichment into their product, where deliverability and freshness matter more than phone coverage and intent, real-time enrichment is worth testing side by side. Check out the Generect API and compare results on your ICP data before committing to a ZoomInfo contract.

ZoomInfo API Setup: The Practical Path

If you decide ZoomInfo is the right fit, this is the realistic path:

  1. Pick the access route: start on the free GTM AI tier to test the API, MCP or CLI. Go through ZoomInfo sales for an Enterprise package if you need volume, mobile data, SSO or custom limits. Have legal review renewal and notice terms before you sign.
  2. Create the app: in the Developer Portal (Enterprise) or the GTM.ai Developer tab (self-serve), create a Standard App, choose the OAuth flow and scopes and store the client ID and secret securely.
  3. Test access: use Test API Access to get a token, make a first Search call and confirm your scopes cover the endpoint families in your package.
  4. Build the integration: native CRM integrations are fastest; custom pipelines or product features take longer, especially with Search plus Enrich match logic and 429 handling.
  5. Target the new API: with the Legacy Enterprise API being deprecated, build against the docs.gtm.ai endpoints from the start.
  6. Monitor consumption: track requests, records and credits against your limits with the Usage Data endpoint. Automated enrichment can drain credits faster than expected.

Common Pitfalls to Avoid

Most ZoomInfo API problems come from a few avoidable mistakes:

  • Underforecast credit usage. Teams size contracts on initial estimates, then run automated workflows that enrich far more records than planned. Model worst-case usage (one credit per record) before you sign.
  • No email validation layer. A match is not proof of deliverability. Add a validation step before high-volume sending to protect sender reputation.
  • Building on the legacy API or JWT. New integrations should use OAuth 2.0 on the new platform. Legacy is being deprecated.
  • Ignoring the hourly cap. A client tuned only to the per-second limit will hit the hourly window and stall on long Retry-After waits.
  • Skipping the SMB and non-US test. Coverage varies by segment and country. Test those records before signing.
  • Ignoring the renewal window. Notice periods on auto-renewal catch teams off guard. Mark the date the day you sign.

Verdict: Is ZoomInfo API Worth It in 2026?

ZoomInfo’s API is strong at what it is designed for: enterprise B2B data enrichment with strong phone coverage, intent signals and an integrated GTM platform.

The 2026 picture:

  • New GTM API at docs.gtm.ai with OAuth 2.0; the JWT-based Legacy Enterprise API is being deprecated
  • Builder 5, Standard 25 and Scaling 35 requests per second, with hourly and daily caps
  • Free search; 1 data credit per new enriched record, re-enrichment free for 12 months
  • Free self-serve tier and pay-as-you-go top-ups; Enterprise pricing is custom
  • MCP, CLI, Agents and Context APIs for AI-assisted workflows
  • Vendor-run test (Cleanlist, 1,000 leads): 84% email and 67% mobile match

If cold calling is your primary channel, intent signals drive your targeting and you want a consolidated platform, ZoomInfo earns its premium.

If you are email-first, budget-constrained or need verified emails for high-volume automated outreach, compare cost per usable record across ZoomInfo, Apollo, a waterfall tool and a real-time API such as Generect on the same 200 records. The cheapest provider per lookup is not always the cheapest per usable contact.

A pragmatic path for many B2B teams: use ZoomInfo for the accounts where phone outreach and intent timing matter, and a lower-cost email enrichment layer for broader pipeline coverage. You do not have to pick one.

Ready to see how your ICP compares? Run a test on Generect: no enterprise contract, no seats, and you will see where real-time enrichment works on your own contact data.

Frequently Asked Questions

How much does the ZoomInfo API cost?

ZoomInfo’s GTM AI pricing page lists a free tier with 1,000 data credits and 1,000 AI credits, then pay-as-you-go top-ups from $20 with no seat fees. Its own example prices enriching 500 CRM leads at 500 data credits, $215. Search and lookup are free, and each new enriched record costs one data credit. Enterprise packages with annual volume, mobile data and custom limits are priced by sales and not published.

What are ZoomInfo’s API rate limits?

On the new platform, ZoomInfo documents Builder at 5 requests per second (10,800 per hour, 129,600 per day), Standard at 25 (54,000 per hour, 648,000 per day) and Scaling at 35 (75,600 per hour, 907,200 per day). All three windows apply at once and a breach returns 429 with Retry-After. The Legacy Enterprise API used 1 request per second for authentication, 25 for standard APIs and 33 for scaling APIs. Contracts also set request and record limits.

Does the ZoomInfo API use OAuth or JWT?

The new ZoomInfo API uses OAuth 2.0: Authorization Code with PKCE for apps acting for signed-in users and partner apps, and Client Credentials for server-to-server integrations. JWT (from a client ID plus private key or from a username and password, valid for one hour) is the authentication method of the Legacy Enterprise API, which ZoomInfo is deprecating.

What email accuracy does ZoomInfo’s API deliver?

ZoomInfo does not publish one accuracy number for the API. In a vendor-run test by Cleanlist on 1,000 B2B leads, ZoomInfo matched 84% of emails and 67% of mobile numbers, against 78% and 41% for Apollo. A match rate is not deliverability, so validate emails before high-volume sending and run your own test on your ICP.

Is there a ZoomInfo API free tier?

Yes. As of October 2026, ZoomInfo’s GTM AI pricing page lists a free tier with API, MCP and CLI access, 1,000 data credits and 1,000 AI credits, a 5 requests per second limit and up to 5 apps, with no credit card required. Mobile phone data, custom limits and SSO are listed for Enterprise packages. For lower-commitment comparisons, Apollo, People Data Labs, Hunter and Generect also offer self-serve options.

Should I build on ZoomInfo’s legacy API or the new API platform?

Build on the new platform documented at docs.gtm.ai. ZoomInfo’s legacy documentation says the Legacy Enterprise API is in the process of being deprecated and that all new development should use the new API. If you have existing legacy integrations, plan the move from JWT to OAuth 2.0 and the new endpoints into your contract timeline.