ZoomInfo API review

What each call costs, in data credits and AI credits

ZoomInfo runs two currencies. Data credits pay for records: enriching a contact, a company or a company's intent signals. AI credits pay for research agents that read across ZoomInfo data and your CRM and write a briefing back. Everything you use to find records is free.

Two prices sit behind that table. A data credit is $0.38 at the $1,000 spend tier, and ZoomInfo's own worked example prices 500 enrichments at $215, which is $0.43 each, so the rate falls as the purchase grows. An AI credit is a flat $0.05, and the pricing page sizes 2,000 of them at about 200 account or contact research calls, roughly ten credits, or 50 cents, a call.

ZoomInfo API pricing, plan by plan

ZoomInfo API pricing now comes in two forms: a published pay-as-you-go rate through GTM AI, and quoted annual packages for everything else.

The packages and the self-serve route meter the same unit differently. The API documentation says package customers buy credits in bulk on an annual basis. The pricing page FAQ describes a package as including "a predetermined number of monthly credits" and adds that what a credit costs depends on the depth of data the package covers. Read both as the same thing from two sides: an annual purchase, drawn down month by month, at a price per credit set by what the package unlocks.

Three windows at once, set by package

ZoomInfo API rate limits are checked against three windows simultaneously, per second, per hour and per day, and a request has to fit all three. The hourly and daily caps sit well below what the per-second rate would allow if you held it all day, which is deliberate.

The ZoomInfo API rate limits are generous for enrichment, where 25 records a call at 25 calls a second outruns any credit budget a self-serve account will hold. They matter for search-heavy agents, where the daily cap on a Builder-sized allowance is the number to plan around.

How to create a ZoomInfo API key

How to get a ZoomInfo API key: in the new API there is no static key. ZoomInfo uses OAuth 2.0, so you create an application in the ZoomInfo Developer Portal and exchange its credentials for a short-lived token. Your subscription decides which scopes and endpoints the application can reach, which is what ZoomInfo API access means in practice.

For a scheduled enrichment job, client credentials on a dedicated integration user is the whole setup. Anything an assistant does on a person's behalf belongs on the authorization code flow or the MCP server, where ZoomInfo can see who asked.

What a ZoomInfo API call looks like

The base URL is api.zoominfo.com/gtm, bodies follow the JSON:API convention with the application/vnd.api+json content type, and the pattern is search, then enrich. Search is free and returns IDs and hints of what data exists; enrich spends a credit per new record and returns the email and phone.

# 1. free: find the people, no contact data yet
POST https://api.zoominfo.com/gtm/data/v1/contacts/search?page[size]=25
Authorization: Bearer $ZOOMINFO_TOKEN
Content-Type: application/vnd.api+json

# 2. paid: enrich only the IDs you kept, 25 at most
POST https://api.zoominfo.com/gtm/data/v1/contacts/enrich
# 1 data credit per record enriched for the first time

Where the ZoomInfo API documentation lives

The ZoomInfo API documentation now lives on two hosts, and the ZoomInfo API docs most search results surface are the old ones. docs.zoominfo.com redirects to docs.gtm.ai, which is the current reference for the GTM API, the MCP server and the CLI, and serves every page as Markdown with an llms.txt index. api-docs.zoominfo.com is the legacy ZoomInfo Enterprise API, still documented and marked as being deprecated.

Two of the legacy names still carry search demand. The ZoomInfo WebSights API resolves an IP address to a company and is documented in the legacy reference beside the Compliance API, which handles opt-outs for contacts in the ZoomInfo database. The ZoomInfo developer API in the new sense is the Developer Portal at developer.zoominfo.com, where applications are created, and the OpenAPI specification can be downloaded from the new reference for Postman or any other client.

The MCP page lists ZoomInfo's MCP access alongside the others in this directory.

ZoomInfo's own walkthrough of the API

ZoomInfo publishes this on its own channel, so it is ZoomInfo's account of ZoomInfo, not ours. It is here because a rate card cannot show you the thing moving, and a few minutes of the product is faster than any paragraph on this page at telling you whether the shape of it fits yours.

Four minutes of ZoomInfo's founder building an enrichment app against the Enterprise API with Claude Code. It is a demo of what an AI assistant does with the API, and the description names the walls it hit: a bad authentication flow, the wrong endpoint and a field name that broke every contact match. It shows nothing about credits, rate limits or price, and the Enterprise API it uses is the one ZoomInfo now marks as legacy, so read this page's request and pricing sections rather than the video for those.

Published 20 March 2026 on ZoomInfo, the channel ZoomInfo's own pages link to, and read on 23 October 2026. Nothing in it is a source for a price or a limit on this page: every figure in the tables above comes from a ZoomInfo page.

Strengths and limits

ZoomInfo is still the depth answer in this directory, and the self-serve route has removed the worst of the old objection.

The two columns describe a vendor in the middle of changing how it sells. The API, the MCP server and the price are now the kind of thing a developer can evaluate alone, and the fields that made ZoomInfo expensive, the mobiles above all, are still where the sales call starts.

Who should actually use this

Use the ZoomInfo API through GTM AI when you want to test ZoomInfo's data against your own rows without a sales process. A thousand free data credits is the largest free allowance of any enrichment vendor in this directory, the search calls cost nothing, and the MCP server means an agent can be pointed at it in one command. That is the right first step even for a team that expects to end up on a package.

Do not pick it on unit price. At $0.38 a data credit the self-serve rate is about nineteen times Apollo's $0.0196 and well above Lusha, RocketReach or LeadMagic for an email, and it carries no mobile numbers at all. ZoomInfo earns its cost on depth, on North American enterprise accounts, org charts and intent, and the self-serve price is for proving that depth rather than for buying volume.

If phones are the job, budget for the Enterprise conversation from the start, and take the match rate you measured on the free credits into it. The published price has changed what a ZoomInfo negotiation starts from: the vendor now has a public number for the email-and-firmographics row, and the quote for everything else has to be argued against it.

Before you build against it

Five things to settle first, each one read off ZoomInfo's own pages. The ticks are remembered in this browser, so you can come back to a half-finished integration.

If ZoomInfo is not the answer

Four providers in the Enrichment APIs listing that solve the same problem differently. Each one is a trade, and the trade is named.

The full set, organized by the reason people leave, is on the ZoomInfo alternatives page.

ZoomInfo against the obvious rival

Same rate cards, read side by side, with the arithmetic done on a worked volume rather than left to you: Apollo vs ZoomInfo, Cognism vs ZoomInfo and Lusha vs ZoomInfo.

The same again, against the rest of the field: UpLead vs ZoomInfo, RocketReach vs ZoomInfo and Clearbit vs ZoomInfo. Every pairing in the directory is on the compare hub.