---
name: instantly-reverse-contact-integration
description: Connect Instantly 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 Instantly and Reverse Contact together, or asks why data is not moving between them.
---

# Instantly and Reverse Contact

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

**What you have to buy first:** A Reverse Contact API key and an Instantly API v2 key with the right scopes

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

## The short version

Instantly is where a bulk enrichment pass stops being a planning exercise. Six thousand requests a minute across the workspace is ten times what Salesloft allows a whole team and a hundred times what Smartlead allows on Standard, so the shape of the build is simply enrich everything and upload. The interesting unknown is the provider registry, which documents a bring-your-own-key model with a cost of zero on the workspace key, and which names no providers publicly. Worth one email to Instantly before building the pipeline the long way.

## Which Instantly limit actually applies to each call

Rows: The call you are making. Columns: What governs it. Instantly publishes 6,000 requests a minute and 100 a second for the whole workspace, shared between API v1 and v2 and across every key. That figure is generous enough to be misleading, because several routes carry their own much tighter limit and the headline one never applies to them.

| The call you are making | The 6,000 a minute workspace budget | Safe to call in a tight loop | Safe to run beside another bulk job |
|---|---|---|---|
| Adding leads to a campaign | Yes | Yes | Partly |
| Reading or updating a lead | Yes | Yes | Partly |
| Listing emails | No | No | No |
| A test send | No | No | No |
| The AI reply label test | No | No | No |

- **Yes.** Governed by the headline limit, which is 100 requests a second and 6,000 a minute. At that rate the Instantly side of this build is never the constraint, and Reverse Contact credits are the only budget left to respect.
- **Partly.** The budget is a workspace budget shared between API v1 and v2 and across every key in it, so two bulk jobs running at once halve each other rather than each receiving the headline figure. Instantly recommends batches of 100 two seconds apart for exactly this reason.
- **No.** Has its own much tighter limit instead: listing emails is 20 requests a minute, a test send is 10 a minute, and the AI reply label test is 500 per 30 days per workspace. No amount of headroom on the headline figure touches these three.

Counted off that grid, of fifteen pairings: four give you yes, two give you partly, nine give you no.

The bottom three rows are the finding, and the practical reading is that Instantly is extremely fast at the two things this build does and slow at the things you would use to check on it. So verification by polling is the wrong instinct here: read the rendered email on one lead instead, which costs one request and tells you more than a loop over the listing endpoint ever will.

## What actually syncs

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

| What | Direction | What that means in practice |
|---|---|---|
| The list, before upload | One way, out | Enrich each row from its email with /v2/enrich/persons. 2 credits on a match, free on a check. |
| Lead upload | One way, in | POST the enriched leads into the campaign with their custom variables. |
| Webhook events | One way, out | Typed events fire back out on campaign activity, which is how a reply reaches a CRM. |
| Anything back to Reverse Contact | One way, out | Nothing. This is a read layer, and your pipeline decides which variables get written. |

## Which field lands where

Everything happens outside Instantly: enrich the row, then upload it. The limits barely constrain this, so what is worth laying out is which values become which fields and which parts of the response should stop a row being uploaded at all.

| In Instantly | In Reverse Contact | What to know about the match |
|---|---|---|
| An email on the row | POST /v2/enrich/persons, 2 credits | Identity, the current role, history, education, skills and location on one schema. A confident null costs nothing, because Reverse Contact charges 0 credits on every 4xx and 5xx. |
| A company domain | POST /v2/enrich/companies, 2 credits | Firmographics from a domain or a company name. Once per company rather than once per lead at it. |
| A profile URL already on the row | POST /v2/fetch/persons, 1 credit | Half the credits, and unmetered from the $249 plan rather than the $699 one. The cheapest route into this pair if your list was sourced from profiles. |
| currentPosition.title and company.name | Custom fields on the lead | The two values most openers reference. The names have to match the sequence variables, and a near-miss renders the fallback rather than erroring. |
| An API v2 key | Scoped per resource | An endpoint refuses a key lacking the relevant scope, which is the right behaviour and means an all:all key in development hides a production failure. |
| The provider registry | credentialSource and effectiveCostPerAction | Documented as a shape rather than a list: workspace_key, instantly_key or unavailable, with a cost of 0 on a workspace key. Which providers it holds is not published, so treat a bring-your-own-key route as a question rather than a capability. |
| Add leads to a campaign | Batches of 100, two seconds apart | Instantly's own recommendation, and worth following under a generous ceiling because the ceiling is shared across every key in the workspace and with API v1. |
| Anything outbound to Reverse Contact | Only what your pipeline sends | This is a read layer. No lead, campaign or reply is sent anywhere, and there is nothing in the product to send it to. |

### The fields that should stop an upload rather than improve one

This matters more on this page than on any other in the set, for a reason that sounds backwards: nothing in the Instantly limits will slow a mistake down. Six thousand requests a minute means a suppression rule you forgot to write reaches thousands of people before anybody notices.

| In the response | Why it is a reason not to send |
|---|---|
| isInRemembrance | The person has died. No amount of personalisation makes the email acceptable, and it is the one outbound failure that cannot be apologised for afterwards |
| currentPosition.companyName disagrees with your record | They have changed job, so a campaign written for the old role is about to reach the new one. Re-qualify rather than refresh |
| isOpenToWork | They are looking to leave. A reason for a human to read the opener once, rather than an automatic stop |
| data is null, with a confidence score | Nothing matched confidently. Sending the fallback text is a decision, and on a cold list it is usually the wrong one |
| metadata.updatedAt, from long ago | Stale rather than wrong, which is the one case where a 2-credit live refresh earns its money |
| followersCount and hasVerificationBadge | Not suppression at all. Listed because they are the fields teams reach for as a seniority proxy, and neither is one |

**What does not cross:**

- An app inside Instantly. There is none, which is consistent with Reverse Contact maintaining apps on Clay, Zapier and Make and nothing inside any CRM or sequencer.
- A published list of registry providers. Instantly documents the registry's shape, including the three credentialSource values and the zero cost per action on a workspace key, and names no providers.
- A business email or a direct phone number from Reverse Contact. Both are separate endpoints at 3 and 20 credits, charged only when one is found.
- Anything that repairs an email already sent. Personalisation renders at send time, so enrichment after the upload improves later steps and nothing before them.

## Connect it, in this order

**Who has to do it:** Whoever can create an API v2 key with the right scopes, plus whoever can create a Reverse Contact key. No admin elsewhere.
**How long:** An afternoon. This is the least constrained of the five sender pairs and the shortest build on the hub.

### 1. Ask Instantly about the provider registry before you build the long way

*Where:* An email to Instantly

Instantly documents an integration provider registry with credentialSource values of workspace_key, instantly_key and unavailable, and an effectiveCostPerAction of 0 on a workspace key. It does not publish which providers are in it. One email could replace this entire pipeline with a key paste, so it is worth sending before an afternoon is spent.

### 2. Decide to enrich before the upload, not after it

*Where:* Your own pipeline

Personalisation renders at send time, so a lead uploaded without the fields a sequence references gets the fallback and nothing later repairs the email that went. Enriching first also lets you drop the rows that did not resolve rather than sending to them.

### 3. Create the key with the narrowest scopes that work

*Where:* Instantly: API v2 keys

API v2 keys carry scopes per resource, and an endpoint refuses a key that lacks the right one. A pipeline built and tested with an all:all key can fail on a narrower production key, which is correct behaviour and an easy afternoon to lose. Test on the key you will ship.

### 4. Check before you fetch, on the endpoint that costs nothing

*Where:* POST /v2/fetch/persons/check

The free check says whether a profile is cached and when it was last updated, so a bulk pass spends 2 credits only where it has to. With 6,000 requests a minute available on the Instantly side, Reverse Contact credits are the only budget this build has to respect.

### 5. Write the suppression rule before the enrichment rule

*Where:* Your pipeline

A current employer that disagrees with your record, an isInRemembrance flag, a confident null: each is a row to drop rather than a row to personalise better. This matters more here than anywhere else in the set, because nothing in the limits will slow you down enough to notice.

### 6. Batch in hundreds anyway, with a pause between them

*Where:* Your pipeline

Instantly recommends batches of 100 with a 2-second wait between them, and running automations several times a day rather than once. Worth following under a generous ceiling, because the ceiling is shared across every key in the workspace and with API v1 as well.

### 7. Keep the tight endpoints out of the loop

*Where:* Instantly: the per-endpoint limits

Listing emails is 20 requests a minute, a test send is 10 a minute, and the AI reply label test is 500 per 30 days per workspace. The headline figure does not apply to every route, so check the one you intend to call repeatedly.

### 8. Send one lead and read the rendered email

*Where:* Instantly: a campaign with one mailbox

The rendered first email is the only artefact that proves the mapping worked. The API reporting success means the lead was accepted, which is a different claim, and the two are easy to confuse at six thousand requests a minute.

The first step is the only one with real leverage and it is an email rather than a task. Everything else is the same build as the other four senders with the constraints removed, which makes the suppression rule in step five the thing that matters most: [the Smartlead version](pair:smartlead+reverse-contact) is slow enough that a mistake gets noticed, and this one is not.

## How to check it worked

- Run the pipeline on the production key rather than the one you developed with. A scope that was never needed in testing is the most likely reason this breaks on the first real run.
- Enrich one row, upload it to a campaign with one mailbox, and read the rendered first email. The rendered email is the only place a mismatched field name is visible.
- Run two bulk jobs at once on purpose and read what happens. The 6,000 a minute is a workspace budget shared with API v1, so two jobs halve each other rather than each getting the headline figure.
- Run a row with a deliberately mismatched current employer through the suppression rule. At this volume an unchecked rule is the one thing that will reach thousands of people before anybody notices.

## 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 pipeline worked in development and fails in production | API v2 keys carry scopes per resource and an endpoint refuses a key that lacks the right one. A development key with broad scopes hides the problem entirely. | Test on the key you intend to ship. The refusal is correct behaviour rather than a fault, which is why nothing in the logs will suggest a permissions problem until you look for one. |
| Two bulk jobs each got half the speed they expected | The limit applies to the entire workspace and is shared between API v1 and v2 even across multiple API keys, so it is not per job and not per key. | Serialise the jobs or accept the halving. Instantly recommends batches of 100 with a 2-second wait and running automations several times a day rather than once. |
| 429 from one endpoint while everything else runs fine | Several routes carry their own limit regardless of the headline figure: listing emails is 20 a minute, a test send is 10 a minute, and the AI reply label test is 500 per 30 days per workspace. | Take those out of any loop. No upgrade or pacing on the main budget affects them, because they are not governed by it. |
| The email went out with fallback text instead of the enriched value | Personalisation renders at send time from whatever the lead record holds, and a field name that does not match the sequence variable renders the fallback rather than failing. | Send one lead to a campaign with one mailbox and read the rendered email. It is the only place this is visible and it costs one request. |
| Thousands of people got an email they should not have | At 6,000 requests a minute a missing suppression rule has no natural brake. Nothing in the limits slows a bad rule down enough for anybody to notice it first. | Compare currentPosition.companyName against your own value and check isInRemembrance before upload, not after. On this pair that rule is worth more than any personalisation it prevents. |
| Nobody can tell you which providers the registry holds | Instantly documents the registry as a shape rather than a list: credentialSource of workspace_key, instantly_key or unavailable, and an effectiveCostPerAction of 0 on a workspace key. The providers themselves are not published. | Ask Instantly directly before building the pipeline the long way. A bring-your-own-key route would replace most of this page, and it is one email rather than an investigation. |
| Everything stopped, including the calls that were free | Below 2 Reverse Contact credits the free Check endpoints are paused as well and answer 402 NO_CREDITS, because the fetch a check precedes can itself cost 2. | Branch on quotas.workspace.credits.left, which rides on every response. GET /v2/usage keeps answering whatever the balance, so a balance check never fails for the reason the lookup did. |
| A quarter of the credits went in an afternoon | This is the one pair in the set with no external brake. A reverse lookup is 2 credits, the Instantly side allows 6,000 requests a minute, and nothing in between enforces a pace. | Call the free check first and refresh only what is stale, set a per-key rate limit on the Reverse Contact side, and read quotas.workspace.credits.left on every response rather than at the end of the run. |

## What breaks, from the vendors' own docs

- **6,000 a minute, and it is a workspace budget.** A hundred requests a second and 6,000 a minute, shared between API v1 and v2 and across every key in the workspace. Generous, and still shared, so two bulk jobs running at once halve each other rather than each getting the headline figure.
- **A few endpoints are much tighter.** Listing emails is 20 requests a minute, a test send is 10 a minute, and the AI reply label test is 500 per 30 days per workspace. The headline limit does not apply to every route, so check the one you intend to loop over.
- **The provider registry names no providers publicly.** Instantly documents the shape of the registry, including credentialSource values of workspace_key, instantly_key and unavailable, and an effectiveCostPerAction of 0 on a workspace key. It does not publish which providers are in it. Treat a bring-your-own-key route as a question for Instantly rather than a documented capability.
- **Scopes are granular, so a key can be silently insufficient.** API v2 keys carry scopes per resource, and an endpoint refuses a key that lacks the right one. A pipeline that worked in testing with an all:all key can fail on a narrower production key, which is the correct behaviour and an easy afternoon to lose.
- **The documented bulk advice is batches of 100.** Instantly recommends batching in hundreds with a 2-second wait between batches, and running automations several times a day rather than once. Worth following even under a generous ceiling, because the ceiling is shared with everything else in the workspace.

## 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

- Instantly API: rate limits: https://developer.instantly.ai/getting-started/rate-limit
- Instantly API: authorization: https://developer.instantly.ai/getting-started/authorization
- Instantly API: integration provider registry: https://developer.instantly.ai/api-reference/supersearchenrichment/returns-the-full-integration-provider-registry
- 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-11, summarised on the page: https://www.reversecontact.com/integrations-hub/reverse-contact-integrations/instantly-reverse-contact-integration#reddit
- This pair, with the reasoning behind each step: https://www.reversecontact.com/integrations-hub/reverse-contact-integrations/instantly-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.*
