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

# Salesloft and Reverse Contact

> Generated from https://www.reversecontact.com/integrations-hub/reverse-contact-integrations/salesloft-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 Salesloft API access through an API key or an OAuth app

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

## The short version

Salesloft enriches the same way Outreach does and meters it completely differently, and the metering is the page. Six hundred cost a minute for the entire team means an enrichment sweep is not a private decision: it spends the same budget as the CRM sync, the dialler and the conversation intelligence tool. The build itself is ordinary, a webhook on cadence membership, a lookup, a PATCH back. The planning is working out what is already spending the budget before you add to it.

## Why a backfill is a cursor poller rather than a loop

Rows: How you read the records. Columns: Against the 600-point minute. Salesloft is the only sequencer here that charges more for reading later pages, and the surcharge is steep enough to change the architecture rather than the schedule. The column below asks whether a hundred requests fit inside one minute, measured against the documented budget of 600 cost a minute for the whole team.

| How you read the records | A hundred requests fit inside one minute | Room left for the rest of the team | The route Salesloft recommends |
|---|---|---|---|
| Pages 1 to 100, at 1 point each | Yes | Yes | Partly |
| Pages 101 to 150, at 3 points | Yes | Partly | No |
| Pages 151 to 250, at 8 points | No | No | No |
| Pages 251 to 500, at 10 points | No | No | No |
| Page 501 and beyond, at 30 points | No | No | No |
| A cursor poller on updated_at | Yes | Yes | Yes |

- **Yes.** A hundred requests at that cost is 100 or 300 points against the documented 600 a minute, so it fits and leaves something behind. The cursor poller stays at the default cost of 1 however deep into the history it goes, which is the whole point of it.
- **Partly.** A hundred requests at 3 points is half the team's minute, which fits and is not polite. Paging to 100 is fine and is still not what Salesloft recommends, because it does not scale past the hundredth page.
- **No.** A hundred requests at 8 points or more is 800 points or worse against a 600-point minute, so it cannot be done inside one minute at all. Three of these rows are identically no, which is the finding: deep paging is not a slow backfill, it is an impossible one.

Counted off that grid, of eighteen pairings: six give you yes, two give you partly, ten give you no.

Three rows reading the same answer is the point rather than an accident: past page 150 the surcharge stops being a tax and becomes a wall. Salesloft says it has found that most customers succeed with a cursor poller on updated_at and publishes a guide for building one, which is unusually direct advice from a vendor about not using its own pagination.

## What actually syncs

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

| What | Direction | What that means in practice |
|---|---|---|
| Trigger | One way, out | A webhook on person_created, or cadence_membership_created to catch someone as they enter a cadence. |
| The enrichment | One way, out | POST /v2/enrich/persons with the person's email. 2 credits on a match, nothing for a freshness check. |
| Write-back | One way, in | PATCH the Salesloft person with title, company and seniority. Each call draws from the team cost budget. |
| Anything back to Reverse Contact | One way, out | Nothing. This is a read layer, and your middle step decides what Salesloft is allowed to receive. |

## Which field lands where

Nothing is installed inside Salesloft, so a receiver takes the webhook, calls Reverse Contact and PATCHes the answer back. Every one of those Salesloft calls costs against a budget the whole team shares, which is what makes the cost column the interesting half of this mapping.

| In Salesloft | In Reverse Contact | What to know about the match |
|---|---|---|
| A cadence membership webhook | Your receiver | Three retries 15 seconds apart and then marked failed, so accept quickly and enrich asynchronously. Answering the webhook with the enrichment result is the design that breaks during a deploy. |
| Person email address | 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. |
| Account domain | POST /v2/enrich/companies, 2 credits | Firmographics from a domain or a company name. Once per account rather than once per person on it, which also saves the Salesloft reads. |
| A profile URL already on the person | POST /v2/fetch/persons, 1 credit | Half the credits, and unmetered from the $249 plan rather than the $699 one. Worth routing to deliberately wherever the URL is already there. |
| Reading one person | 1 cost, by default | Every endpoint costs 1 unless documented otherwise, and Salesloft reserves the right to change any cost at any time because a cost change does not deprecate anything. |
| Reading page 101 and beyond | 3 to 30 cost, rising by page range | The one documented surcharge: 3 points for pages 101 to 150, 8 for 151 to 250, 10 for 251 to 500 and 30 past 500. This is why a backfill is a cursor poller rather than a loop. |
| Writing the enriched fields back | PATCH a person, 1 cost | Cheap per call and still part of the team budget. Collapse the write into one request per person rather than one per field. |
| Anything outbound to Reverse Contact | Only what your receiver sends | This is a read layer. No person, cadence or call is sent anywhere, and there is nothing in the product to send it to. |

### The fields that should stop a send rather than improve one

The rest of this directory treats an enrichment response as values to write. On a sequencer it is also a list of reasons not to send, and that half is almost never built. Each row is a documented field, and each is a person who should leave the cadence rather than receive a better-written version of the same email.

| 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 the account | They have changed job, so the cadence 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 Salesloft. There is no listing and no in-product step that calls an external API, which is consistent with Reverse Contact maintaining apps on Clay, Zapier and Make and nothing inside any CRM or sequencer.
- A distributed integration built on an API key. Keys are for customers only, so anything shared with another team has to be an OAuth application.
- A business email or a direct phone number. Both are separate endpoints at 3 and 20 credits, charged only when one is found.
- Anything that repairs a sent email. Steps render at send time, so enrichment after cadence entry improves what comes next and nothing that has gone.

## Connect it, in this order

**Who has to do it:** A Salesloft admin if you need the client credentials flow, plus whoever hosts the receiver and whoever can create a Reverse Contact API key.
**How long:** A day and a half. Finding out what else is already spending the team rate limit is a conversation rather than a task.

### 1. Find out what else holds API credentials on the team, before you add anything

*Where:* Salesloft: your own integrations list, and a conversation

The rate limit is 600 cost a minute at team level, and Salesloft states plainly that one integration can affect another's limit. So the budget you are designing against is already partly spent by the CRM sync, the dialler and anything else connected. This is the step with no screen and it is the one that decides the design.

### 2. Decide where enrichment sits relative to cadence entry

*Where:* Your own process

Steps render from the record at send time, so enriching somebody already in a cadence improves later emails and cannot touch the one that has gone. Enrich, then add to the cadence. This is irreversible in the only way that matters: the recipient already read it.

### 3. Choose the auth method on governance grounds, not convenience

*Where:* Salesloft: API keys or an OAuth app

API keys are for your own team only; anything distributed has to be an OAuth application. The client credentials flow for a private app has to be enabled by an admin and then runs with that admin's permissions, which is a question about accountability rather than about tokens.

### 4. Plan the backfill as a cursor poller, not as pagination

*Where:* Salesloft: the updated_at field

Page numbers above 100 cost extra and the surcharge rises steeply. Salesloft recommends a cursor poller on updated_at instead and publishes a guide for it. Taking this decision before you write the loop saves rewriting the loop.

### 5. Make the webhook receiver answer fast and work later

*Where:* Your receiver

A failing webhook gets three retries 15 seconds apart and is then marked failed. Fifteen seconds is not long enough to ride out a deploy, so the receiver has to accept the call immediately and do the enrichment asynchronously rather than answering with the result.

### 6. Check before you fetch, on the free endpoint

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

The free check says whether a profile is cached and when it was last updated, so a sweep spends 2 credits only where it has to. On a shared rate limit this matters twice: fewer Reverse Contact credits, and fewer Salesloft calls to re-read records you were never going to refresh.

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

*Where:* Your receiver

The response carries more reasons not to send than reasons to send: a current employer that disagrees with the account, an isInRemembrance flag, a confident null. Each is a person who should leave the cadence rather than get a better version of the same email.

### 8. Read the cost headers rather than counting calls

*Where:* Every Salesloft API response

x-ratelimit-endpoint-cost reports what the request just cost and x-ratelimit-remaining-minute reports what is left. Each endpoint costs 1 by default and Salesloft can change a cost at any time, on the grounds that a cost change deprecates nothing, so the headers are the only reliable figure.

The first and the fourth steps are the ones that make this build survive contact with a busy team, and neither is about enrichment. That is the pattern on every pair in this directory where a shared budget is involved: the integration is easy and the arithmetic is the work. [Outreach meters per user](pair:outreach+reverse-contact) instead, which removes this whole conversation.

## How to check it worked

- Read x-ratelimit-remaining-minute at a busy time of day rather than at the start of a sprint. That number is the budget you actually have, and it is lower than 600 whenever anything else is running.
- Request page 101 of anything and read x-ratelimit-endpoint-cost. It should come back as 3 rather than 1, which is the cheapest possible demonstration that the pagination surcharge is real.
- Take the receiver down for a minute and fire a webhook at it. Three retries 15 seconds apart means you have 45 seconds before the event is marked failed, and knowing that number changes how you deploy.
- Enrich one person, then open the rendered preview of their next cadence step. The preview is the only place you see what the recipient sees, and a fallback that reads badly is only obvious there.

## 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 |
|---|---|---|
| A 429 on a sweep that worked in a test account | The limit is 600 cost a minute at team level rather than per integration, and Salesloft states that one integration can affect another's limit. A test team has nothing else running on it. | Read x-ratelimit-remaining-minute at a busy hour and design against that figure. A team with many integrations can ask Salesloft to adjust the limit, which is a conversation rather than a setting. |
| The backfill got slower the further it went | Page numbers above 100 carry an additional cost: 3 points for pages 101 to 150, 8 for 151 to 250, 10 for 251 to 500 and 30 past 500. | Rewrite it as a cursor poller on updated_at, which Salesloft recommends and documents. The cost stays at the default of 1 however far back the history goes. |
| A call that used to be cheap is now expensive | Each endpoint has a default cost of 1 and Salesloft can change the cost of an existing endpoint at any time, on the stated grounds that the functionality is not deprecated by a cost change. | Read x-ratelimit-endpoint-cost from live responses rather than holding a table of costs. The header is there precisely because the numbers move. |
| Webhook events are being marked failed during deploys | A failing webhook gets three retries 15 seconds apart and is then marked failed, which gives the receiver about 45 seconds in total. | Accept the webhook immediately, queue the work, and enrich asynchronously. A receiver that answers with the enrichment result cannot survive a restart. |
| The private app stopped working when somebody left | The client credentials flow has to be enabled by an admin and runs with that admin's permissions, so it inherits their account rather than standing on its own. | Use a service account that will outlast an individual, and document whose permissions the integration is actually running with. This is a governance answer rather than a technical one. |
| A well-personalised email reached somebody who changed job | The enrichment wrote a new title and nothing compared the returned current employer against the account the person sits under. | Compare currentPosition.companyName with the account and route disagreements out of the cadence. Three lines in the receiver, and the highest-value check on this page. |
| Everything stopped, including the calls that were free | Below 2 Reverse Contact credits the free Check endpoints are paused too 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 same reason. |
| An endpoint that worked last week returns nothing | /v2/resolve was replaced by /v2/enrich and /v2/search/persons by /v2/search/people, with the old pair documented as live only until 13 October 2026. | Change both paths in the receiver. It is ordinary version-controlled code on this route, which is the one consolation of there being no app to install. |

## What breaks, from the vendors' own docs

- **600 cost a minute, shared across the team.** The limit is per team and not per integration, and Salesloft says explicitly that one integration can affect another's limit. Before adding an enrichment loop, find out what else holds API credentials on that team, because the budget is already partly spent.
- **Endpoint costs can change without notice.** Each endpoint costs 1 by default and Salesloft reserves the right to change a cost at any time, on the grounds that a cost change does not deprecate anything. Read x-ratelimit-endpoint-cost from live responses rather than assuming a call still costs what it cost last quarter.
- **Deep pagination is expensive on purpose.** Page 101 to 150 costs 3 points a request, 151 to 250 costs 8, 251 to 500 costs 10, and past 500 costs 30. A backfill that walks pages is therefore quadratically worse than one that uses a cursor poller on updated_at, which is what Salesloft recommends instead.
- **API keys will not get a partner app approved.** Keys are for customers only. Anything distributed has to be an OAuth app, and the client credentials flow for private apps has to be enabled by an admin and runs with that admin's permissions, which is a governance question rather than a technical one.
- **A failing webhook gets four attempts and stops.** Three retries, 15 seconds apart, then marked failed. Fifteen seconds is not long enough to ride out a deploy, so the receiver needs to accept quickly and do the enrichment asynchronously rather than answering the webhook with the result.

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

- Salesloft: API rate limits: https://developer.salesloft.com/docs/platform/api-basics/rate-limits/
- Salesloft: webhook event types: https://developer.salesloft.com/docs/platform/webhooks/event-types/
- Salesloft: API basics and authentication: https://developer.salesloft.com/docs/platform/api-basics/
- Salesloft: building an efficient cursor poller: https://developer.salesloft.com/docs/platform/guides/building-an-efficient-cursor-poller/
- 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/salesloft-reverse-contact-integration#reddit
- This pair, with the reasoning behind each step: https://www.reversecontact.com/integrations-hub/reverse-contact-integrations/salesloft-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.*
