---
name: zoominfo-reverse-contact-integration
description: Connect ZoomInfo and Reverse Contact: what syncs, which editions carry it, the setup order, and the failures to expect. Covers contacts, companies. Use when the user wants to set up, audit or troubleshoot ZoomInfo and Reverse Contact together, or asks why data is not moving between them.
---

# ZoomInfo and Reverse Contact

> Generated from https://www.reversecontact.com/integrations-hub/zoominfo-integrations/zoominfo-reverse-contact-integration
> Every tier requirement, sync direction and limit below was read from the vendors' own documentation on 2026-10-28.
> Vendors change these without notice. Re-check anything load-bearing before you rely on it.

**What you have to buy first:** A ZoomInfo contract with API access, a Reverse Contact API key, and an orchestrator to run the waterfall

**What moves:** contacts, companies, one way, out of ZoomInfo.
**How it is built:** built on the api, zapier, make or n8n. **Effort:** hours.

## The short version

The interesting difference between these two is not coverage, it is the meter. ZoomInfo charges one credit the first time it enriches a record in a rolling twelve months and then places that record under management, so re-enriching it is free for a year. Reverse Contact charges per call and stops metering whole endpoint families at a plan price. Those models reward opposite behaviours, and the question that decides which suits you is how often you intend to refresh, which almost nobody asks before signing either contract.

## Two meters, and the behaviour each one rewards

Rows: What you do. Columns: What it costs on each meter. These products are usually compared on coverage, which decides nothing, and rarely on metering, which decides the bill. The rows are the things a team actually does and the columns are what each does to each meter. Every figure is from the vendor's own documentation, read on the new ZoomInfo docs host.

| What you do | On ZoomInfo's record meter | On Reverse Contact's call meter | Counts against a separate limit | Can stop being metered |
|---|---|---|---|---|
| Enrich a record for the first time | One credit | One credit | The record limit too | Unmetered from $699 |
| Re-enrich the same record a month later | Nothing | One credit | The record limit too | Unmetered from $699 |
| Search for people you do not hold | Nothing | One per profile | No | Unmetered from $449 |
| Resolve a profile URL you already hold | Not what it is for | One cached credit | No | Unmetered from $249 |
| Find a missing phone number | One credit | Only on a result | The record limit too | Always on credits |

- **One credit.** One credit on that meter. ZoomInfo consumes one the first time a record is enriched in a rolling 12-month period; Reverse Contact charges 2 for a reverse lookup from an email, a name or a domain.
- **Nothing.** Free. ZoomInfo lists Lookup, Search Companies, Search Contacts and the Find Similar and Find Recommended operations as consuming no credits, and a record under management can be re-enriched for a year without another credit.
- **One cached credit.** A cached lookup from a profile URL is 1 credit, half the price of a reverse lookup, and the cheapest route to a full record anywhere in this directory.
- **One per profile.** Reverse Contact charges 1 credit per profile delivered by a search, and nothing at all for the count endpoint that tells you how large the result set is before you pay for it.
- **Only on a result.** Find Email at 3 credits and Find Phone at 20 are charged only when something is found, and both are asynchronous, returning a task id to poll with check_task.
- **Not what it is for.** Not what this product is sold for. ZoomInfo is bought to search a database rather than to resolve a profile URL you already hold, so the comparison does not apply to that row.
- **The record limit too.** ZoomInfo says each enrichment counts against the customer's record limit, including the re-enrichments that consume no credit. Free of credits is not free of the limit, and the two budgets run out at different times.
- **No.** No separate record limit applies on the Reverse Contact side. The constraint there is the 100,000 profile per workspace per UTC day ceiling on the Unlimited plans, which applies to the covered calls as a whole.
- **Unmetered from $249.** Cached lookups from a profile URL stop being metered on Go at $249 a month.
- **Unmetered from $449.** People and company search stops being metered on Plus at $449 a month.
- **Unmetered from $699.** Reverse lookups from an email, a name or a domain stop being metered only on Max at $699 a month.
- **Always on credits.** Stays on credits on every plan, including Platform, where it moves to a volume rate. ZoomInfo meters out of annually purchased bulk credits throughout, with no equivalent of an unmetered family.

Counted off that grid, of twenty pairings: four give you one credit, two give you nothing, one gives you one cached credit, one gives you one per profile, one gives you only on a result, one gives you not what it is for, three give you the record limit too, two give you no, one gives you unmetered from $249, one gives you unmetered from $449, two give you unmetered from $699, one gives you always on credits.

The second row is the whole grid: re-enriching a record you already paid for is free on ZoomInfo and full price on Reverse Contact, so a team that refreshes a stable list every month is on the wrong meter if it moves. Read the third column with it, because free re-enrichment still spends the record limit, and the fourth is the opposite case, where paying for a plan rather than for calls removes the meter entirely from whichever family matches the identifier your list carries.

## What actually syncs

Direction is written from ZoomInfo's point of view: out means out of ZoomInfo, in means into it.

| What | Direction | What that means in practice |
|---|---|---|
| Nothing | One way, out | No sync between two data providers, no app on either side, nothing to configure between them. |
| The first call | One way, out | Whichever provider the identifier and the budget favour, run from Clay, n8n or your own code. |
| The fallback | One way, out | The other provider, on the rows that came back empty. The only sense in which these two are connected. |
| The verification | One way, out | A separate step before anything is sent, which every practitioner account of this build describes adding. |

## Which field lands where

There is nothing to map between two providers. What is worth laying out is what each call costs, what is free on each side, and what the published figures count, because the coverage numbers here differ by more than any other pairing in the directory and compare the least.

| In ZoomInfo | In Reverse Contact | What to know about the match |
|---|---|---|
| A record enriched for the first time this year | ZoomInfo: 1 bulk data credit, then free for a year | The record is placed under management for a rolling 12 months and can be re-enriched without another credit, though each enrichment still counts against the record limit. |
| A search, or a lookup | ZoomInfo: free | Lookup, Search Companies, Search Contacts, Find Similar Companies, Find Similar Contacts and Find Recommended Contacts consume no credits. |
| An email, a name or a domain | Reverse Contact: 2 credits, unmetered from $699 | Identity, current role, history and the company on one schema. A miss returns null with a confidence score and costs nothing. |
| A profile URL | Reverse Contact: 1 credit, unmetered from $249 | Half the price, same schema. On a list sourced from profiles this is the single largest lever on the bill. |
| A freshness check | Reverse Contact: free, and the fairest tiebreak | Says whether a profile is cached and when it was last updated. Use it when two providers disagree, because the answer is usually a refresh date. |
| A missing email or phone number | Reverse Contact: 3 and 20 credits, on a result only | Both asynchronous, returning a task id to poll, and both stay on credits on every plan including Platform. |
| Either provider's answer | A verifier, before a sequence | This is ZoomInfo's stated objection to waterfalls and the right answer to it. Resolved is not deliverable on any provider. |
| Anything between the two | Nothing at all | No sync, no app, no shared object. The orchestrator is the only thing that knows both exist. |

### What each side publishes, and what it counts

This is the largest gap between published figures in the directory and the least informative, because the two vendors count different objects. Each row names who publishes the figure, and the second column says what the number is actually a count of.

| The published figure | What it actually counts |
|---|---|
| ZoomInfo: 500M+ contacts, 100M+ companies | Contact records in a database you search, plus 34M+ companies and 200M+ professionals outside North America. The company figure is the larger of the two sides by a wide margin |
| Reverse Contact: 800M+ profiles, 70M+ companies | Public professional profiles, which are identities you resolve to rather than mailboxes you write to. More people and fewer companies, because it is a different object |
| ZoomInfo: 200M+ verified business emails, 135M+ verified phone numbers, 120M+ direct dials | The figures that are actually comparable to a sequence's needs, and the ones with no counterpart on the other side, because Reverse Contact sells email and phone as separate metered endpoints rather than as corpus size |
| ZoomInfo: 1.5B+ data points processed daily | Throughput of their pipeline. Reverse Contact publishes 200M refreshes a month, which is a different measure again, and neither is convertible into the other |
| Reverse Contact: a 70%+ identity match rate | A global average with the instruction to measure your own on 500 rows. ZoomInfo publishes no match rate figure in the material cited here |
| ZoomInfo, about its competitors | A warning about taking any of this at face value: their own site gives Apollo 270M contacts and 70M companies, while Apollo publishes 240M and 30M. Quote a vendor about itself and nothing else |
| ZoomInfo: the data is "all verified too, not just the first record in a waterfall" | Their argument against the architecture on this page, published on their own site. It is a fair point about ordering and it is answered by verifying rather than by denying it |

**What does not cross:**

- An integration between the two. No app, no sync, no shared object, and a waterfall is something your orchestrator does rather than something either vendor provides.
- A ZoomInfo price. It is quoted rather than listed, so no figure appears on this page and no per-record rate is derived from one.
- A dollar cost per enriched record on either side. ZoomInfo sells credits in bulk annually and Reverse Contact sells packs and plans, and dividing either by a record count would be our arithmetic wearing their authority.
- Intent data and org charts. ZoomInfo sells both and Reverse Contact does not, which is the clearest reason on this page to keep a ZoomInfo contract rather than replace it.

## Connect it, in this order

**Who has to do it:** Somebody who can get API access on the ZoomInfo contract, somebody who can create a Reverse Contact key, and whoever owns the orchestrator.
**How long:** An afternoon to build. Longer to get ZoomInfo API access through procurement.

### 1. Work out how often you intend to re-enrich, because the meters reward opposite answers

*Where:* Your own process, before either contract

ZoomInfo charges one credit per record per rolling twelve months and then lets you re-enrich free; Reverse Contact charges per call. A list you refresh monthly is cheap on the first model and expensive on the second, and a long tail of one-off lookups is the reverse. Nothing later in this checklist matters as much.

### 2. Find out what your record limit is, separately from your credits

*Where:* Your ZoomInfo contract

ZoomInfo says every enrichment counts against the customer's record limit even when a record under management consumes no further credit. So free re-enrichment is free of credits and not free of the limit, and those are two different budgets to plan against.

### 3. Audit which identifier your rows carry

*Where:* Your CRM or your list

A profile URL is 1 credit on Reverse Contact and unmetered from $249. An email, a name or a domain is 2 and unmetered only from $699. On the ZoomInfo side the free operations are the searches and the lookup, while enrichment is what costs, so the audit changes the cost on both sides in different directions.

### 4. Create both credentials, and read the rate limits off a live response

*Where:* ZoomInfo and Reverse Contact

ZoomInfo returns per-second, per-hour and per-day limit and remaining headers on every response according to its rate-limits page, while its credit page says headers are not currently returned. Read them, and have a fallback that works if they are absent.

### 5. Put the provider whose misses are free first

*Where:* Your orchestrator

On Reverse Contact every 4xx and 5xx is 0 credits and the finders are charged only on a result, with a live fetch as the sole exception. On ZoomInfo the searches and the lookup are free and enrichment costs per new record, so discovering what you cannot resolve is cheap on both sides if you order it deliberately.

### 6. Check before you fetch, on the endpoints that cost nothing

*Where:* POST /v2/fetch/persons/check, and ZoomInfo Lookup

Reverse Contact's free check says whether a profile is cached and when it was last updated. On a comparison this is also the fairest tiebreak available, because a disagreement between two providers is usually a difference in refresh date rather than in accuracy.

### 7. Add the verification step before anything is sent

*Where:* A verifier, at the end of the chain

ZoomInfo's objection to waterfalls is that they take the first answer, and the honest response is to verify the answer rather than to deny the objection. Every practitioner account of this build ends with a verifier and neither vendor's quickstart includes one.

### 8. Count resolved, correct and deliverable as three different numbers

*Where:* Your bake-off sheet

A provider can resolve the wrong person, resolve the right person with a dead address, or decline to answer. A single accuracy figure hides all three, and the whole value of a provider that returns null with a confidence score disappears if your count treats a refusal as a failure.

### 9. Decide what a null does, and write it down

*Where:* Your orchestrator

Fall through to the other provider, queue for review, or write nothing. The option that is never right is writing a low-confidence guess into a field a rep will read as a fact, which is the failure the comparison on this page exists to help you avoid.

The first step is the one that decides the economics and it happens before either contract is signed, which is why it is first and why it has no screen attached. Everything after it is an afternoon of orchestration and a week of honest counting, and the counting is what you will be asked to defend.

## How to check it worked

- Enrich the same record twice on ZoomInfo inside the same year and confirm the second one consumes no credit. Then check whether it counted against your record limit, because those are two separate budgets.
- Run the same 500 rows through both providers in both orders. If the order changes the outcome by more than the overlap, the ordering is doing more work than either corpus.
- Deliberately exhaust one ZoomInfo window and watch which bucket is named. The 429 carries X-RateLimit-Rejected-Bucket, so you learn whether the second, the hour or the day is your real ceiling.
- Compare the update dates rather than the values when the two providers disagree. A difference in refresh date explains most disagreements and tells you something a coverage table cannot.

## When it goes wrong

Each row is a symptom somebody reports, the documented reason, and the fix. Work down it before escalating to either vendor, because most of these are configuration.

| Symptom | Why it happens | What to do |
|---|---|---|
| The ZoomInfo credits lasted and the record limit did not | Re-enriching a record under management consumes no credit and still counts against the record limit, which are two separate budgets. | Track both. A refresh schedule designed around the credit model will quietly spend the limit instead, and the limit is the one that is not replenished by not spending credits. |
| A 429 from ZoomInfo while well under the per-second limit | Three windows are evaluated simultaneously, and the hour and day windows are rolling rather than fixed, so a burst an hour ago still counts. | Read X-RateLimit-Rejected-Bucket from the 429, which names whether it was the second, the hour or the day. Rejected requests do not consume quota, so a backoff costs nothing but time. |
| The rate-limit headers are not there | ZoomInfo's two documentation pages disagree: the rate-limits page lists six headers on every response, the credit usage page says headers are not currently returned. | Read them when present and fall back to exponential backoff with jitter when they are not. Note also that the older X-RateLimit-Limit and X-RateLimit-Remaining are deprecated and due for removal on 2027-01-01. |
| A bookmarked ZoomInfo doc now redirects | docs.zoominfo.com returns a permanent redirect to docs.gtm.ai. | Update the citation rather than following the redirect each time. Every ZoomInfo figure on this page was read from the new host on 2026-10-28. |
| The waterfall produced a worse list than the single provider did | A waterfall takes the first answer it receives, so a badly ordered one promotes a weak source above a strong one. This is ZoomInfo's published objection to the architecture. | Order by accuracy rather than by price, and add verification at the end. The objection is sound and the answer to it is a step rather than a different provider. |
| The two providers disagree about where somebody works | Two corpora refreshed on different schedules will differ, and the difference is usually recency rather than accuracy. | Compare update dates instead of values. Reverse Contact's free check returns when the profile was last updated, which settles most disagreements for nothing. |
| 429 DAILY_EXTRACTION_LIMIT_EXCEEDED on an Unlimited plan | Reverse Contact's covered calls are unmetered up to 100,000 profiles per workspace per UTC day and refused until midnight UTC after that. | Spread the job across UTC days. ZoomInfo Standard allows 648,000 requests a day by comparison, and charges per new record, so the comparison is a trade rather than a win either way. |
| A comparison chart does not match either vendor's own site | Vendors publish figures about competitors. ZoomInfo's own site gives Apollo 270M contacts and 70M companies while Apollo publishes 240M and 30M. | Quote a vendor only about itself and measure the rest. A figure nobody will stand behind in their own documentation is not a figure to buy on. |

## What breaks, from the vendors' own docs

- **ZoomInfo meters records, not calls.** Each time a record is enriched for the first time within a rolling 12-month period, one credit is consumed and the record is placed under management for a year, during which it can be enriched again without consuming another credit. Each enrichment still counts against the customer's record limit, and credits are purchased in bulk annually.
- **Three rate-limit windows, all checked at once.** Standard is 25 a second, 54,000 an hour and 648,000 a day; Builder is 5, 10,800 and 129,600; Scaling is 35, 75,600 and 907,200. The hour and day windows are rolling rather than fixed, a request succeeds only if all three have capacity, and rejected requests do not consume quota.
- **Some ZoomInfo operations are free.** Lookup, Search Companies, Search Contacts, Find Similar Companies, Find Similar Contacts and Find Recommended Contacts consume no credits; Enrich Companies and Enrich Contacts cost one bulk data credit per new record. That is the same shape as Reverse Contact's free check and free search count, arrived at independently.
- **Two ZoomInfo pages disagree about rate-limit headers.** The rate-limits page lists six headers returned on every response, with the older pair deprecated and due for removal on 2027-01-01. The credit usage page says rate-limit headers are not currently returned. Both are current and this is their inconsistency rather than ours, so read the headers and have a fallback.
- **The documentation changed host.** docs.zoominfo.com now returns a permanent redirect to docs.gtm.ai, so a citation or a bookmark from before the move points at a 301. Every ZoomInfo figure on this page was read from the new host on 2026-10-28.
- **ZoomInfo pricing is quoted rather than listed.** There is no published price, no published per-record rate and no way to derive one honestly, so this page states none. The rate-limit package names are published and the money is not, which means the throughput you get is knowable in advance and the cost is not.
- **Reverse Contact's Unlimited plans stop at 100,000 profiles a day.** Covered calls cost nothing up to 100,000 profiles per workspace per UTC day, then return 429 DAILY_EXTRACTION_LIMIT_EXCEEDED until midnight UTC. ZoomInfo Standard allows 648,000 requests a day and charges per new record, so the two ceilings are in different currencies as well as different sizes.
- **Neither coverage figure predicts your list.** Reverse Contact publishes 70%+ as a global identity match rate and says to measure your own on 500 rows. ZoomInfo publishes corpus sizes and no match rate. Both are descriptions of a database rather than forecasts about your rows.

## The APIs, if you are building around it instead

### Reverse Contact

- **Base:** `https://api.reversecontact.com/v2`
- **Auth:** `Authorization: Bearer rc_your_api_key`. Keys are created in Workspace > API Keys.

| Call | Request | What it does |
|---|---|---|
| `POST /v2/enrich/persons` | `{ "email": "j.okafor@northwind.io" }` | Resolve a person from an email, a name plus company, or a profile URL. Cached resolution, returns in the response. |
| `POST /v2/enrich/companies` | `{ "domain": "northwind.io" }` | Resolve a company from a domain or a name. |
| `POST /v2/fetch/persons` | `{ "linkedInUrl": "..." }` | Standard profile lookup from the database. |
| `POST /v2/fetch/persons/live` | `{ "linkedInUrl": "..." }` | Live on-demand resolution. ASYNCHRONOUS: returns a webhookId to poll, not a record. |
| `POST /v2/search/people` | `{ "filters": { "currentCompanyDomain": "northwind.io" } }` | Filtered people search. 1 credit a profile delivered, and /v2/search/people/count is free. It replaced /v2/search/persons, which returns 410 Gone since 13 October 2026. |
| `POST /v2/search/organizations` | `{ "filters": { "companyDomain": "northwind.io" } }` | Filtered company search. A domain can also go straight to a company through POST /v2/enrich/companies, or through the enrich_company MCP tool since November 2026. |
| `POST /v2/contact/email` | `{ "linkedInUrl": "..." }` | Find an email. ASYNCHRONOUS: returns a taskId to poll. 3 credits for a professional address, 5 for a personal one, 8 for both, refunded when neither is found. |
| `GET /v2/webhooks/:webhookId` | - | Poll an async job until status is "succeeded". Polling is free and does not count against the rate limit. |

Response shape:

```json
{
  "success": true,
  "data": {
    "person": {
      "fullName": "Jane Okafor",
      "headline": "VP Sales at Northwind",
      "location": "London, United Kingdom",
      "linkedInUrl": "https://linkedin.com/in/...",
      "currentPosition": { "title": "VP Sales", "companyName": "Northwind", "startDate": "2023-04" },
      "emails": [], "experience": [], "education": [], "skills": []
    },
    "company": { "name": "Northwind", "domain": "northwind.io",
                 "industry": "Software Development", "employeeCount": 220 }
  },
  "error": null,
  "metadata": { "requestId": "req_...", "executionTimeMs": 480, "updatedAt": "2026-09-01T..." },
  "quotas": { "creditsConsumed": 1, "workspace": { "credits": { "total": 10000, "used": 4521, "left": 5479 } } }
}
```

**Rules that will cost you time if you skip them:**

- A miss returns **null**, not a best guess. Every response carries a confidence score, and you can raise the precision threshold on the request. Branch on it: do not treat a low-confidence answer as a match.
- Use the cached endpoints anywhere that must answer inside one HTTP request. The `/live` endpoints return a task and need polling.
- `quotas.workspace.credits.left` is on every response. Log it, or you will find out about the balance from a 402.
- Credit costs per call are published and a dollar rate per lookup is not: 2 credits for a reverse lookup from an email, 1 for a cached profile lookup, 2 for a live refresh, 3 for a business email and 20 for a direct phone number, with the last two charged only when one is found. Checks and the search count endpoint are free. Credit packs expire after 3 months. Do not hard-code a dollar cost assumption.

**MCP server:** `https://api.reversecontact.com/mcp`

- Auth: OAuth 2.1 where the client supports it, otherwise `Authorization: Bearer rc_your_api_key`.
- Tools: `enrich_person`, `enrich_person_live`, `enrich_company`, `enrich_company_live`, `search_persons`, `search_companies`, `check_usage`, `check_task`
- Streamable HTTP, JSON-RPC 2.0. The `_live` tools return a task id that `check_task` polls.

Docs: https://docs.reversecontact.com/getting-started

## Sources

- ZoomInfo API: rate limits: https://docs.gtm.ai/docs/rate-limits
- ZoomInfo API: credit usage and limits: https://docs.gtm.ai/docs/credit-usage-and-limits
- ZoomInfo: published coverage figures: https://www.zoominfo.com/about
- Apollo pricing and plan features: https://www.apollo.io/pricing
- Reverse Contact API documentation: https://docs.reversecontact.com/getting-started
- Reverse Contact: credits: https://docs.reversecontact.com/guides/credits
- Reverse Contact: rate limits: https://docs.reversecontact.com/guides/rate-limits
- Reverse Contact pricing: https://www.reversecontact.com/pricing
- 14 practitioner threads read on 2026-10-28, summarised on the page: https://www.reversecontact.com/integrations-hub/zoominfo-integrations/zoominfo-reverse-contact-integration#reddit
- This pair, with the reasoning behind each step: https://www.reversecontact.com/integrations-hub/zoominfo-integrations/zoominfo-reverse-contact-integration

---

*Published by Reverse Contact, which appears in this directory as a data provider.
No other vendor pays for placement. Where a vendor publishes no public figure, this file says so
rather than estimating. Reverse Contact costs are stated in credits, which it publishes; no dollar
rate per lookup appears here, because none is published and dividing a pack price is not their number.*
