Salesloft API review
Best documented cost-based rate limit
GET /v2/people.json?per_page=100&updated_at[gt]=... Authorization: Bearer $SALESLOFT_TOKEN # x-ratelimit-endpoint-cost: 1 # x-ratelimit-remaining-minute: 599 # the same call with page=501 would cost 30
Salesloft is the inverse of most vendors on two axes at once. It publishes no price at all, to the point where its pricing page is titled Talk to Sales, and it documents its rate limit more carefully than almost anything else in this directory. If you are integrating with Salesloft, the commercial conversation is somebody else's problem and the technical one is unusually well specified.
The Salesloft API rate limit is a cost budget rather than a request count. Every endpoint has a cost, the default is 1, and you get 600 cost per minute. The budget applies at the team level, not the integration level, so every tool connected to that team draws on the same 600. Your careful integration can be starved by somebody else's, and Salesloft says so explicitly.
The part worth reading before you write a sync is what happens when you page deeply into a list. Requests with a page parameter above 100 cost more, rising to 30 for page 501 and beyond. That turns a naive backfill, the kind that walks a list page by page until it runs out, from a slow job into one that exhausts the whole team budget in twenty requests.
The rest of the category is in the Sending APIs listing.
What a call costs, and what deep paging costs
Every endpoint carries a cost that is deducted from a 600 per minute budget. The default is 1. The published exception is the page parameter, and it is a steep one.
| Request | Cost | Calls before the budget is gone |
|---|---|---|
| Any endpoint, default | 1 | 600 a minute |
| Page 101 to 150 | 3 | 200 a minute |
| Page 151 to 250 | 8 | 75 a minute |
| Page 251 to 500 | 10 | 60 a minute |
| Page 501 and beyond | 30 | 20 a minute |
Salesloft is open about why: it has found that most customers succeed with a cursor poller on the updated_at field rather than deep pagination, and it publishes a guide to building one. The costs are a nudge toward that pattern rather than a revenue line, since there is no money attached to them. Two response headers tell you where you stand on every call: x-ratelimit-endpoint-cost for what the request just cost, and x-ratelimit-remaining-minute for what is left.
The documentation states this plainly: Salesloft is able to change the cost of an existing endpoint whenever it likes, because a cost change does not deprecate the functionality. That is a reasonable position for them and a real constraint for you. It means an integration sized against today's costs has no contractual protection against tomorrow's, and the only safe design is one that reads x-ratelimit-remaining-minute and adapts rather than one that hard-codes a request rate it believes is safe.
Salesloft API pricing, plan by plan
Salesloft API pricing cannot be reported here, because Salesloft does not publish any pricing at all. The page at salesloft.com that would normally carry a rate card is titled Talk to Sales and contains a form. There is no free tier, no trial price and no per-seat figure anywhere on the site.
| What you might want to know | What Salesloft publishes |
|---|---|
| Price per seat | Not published |
| Plan tiers and what separates them | Not published |
| Whether API access costs extra | Not published |
| Free tier or trial | Not published |
| Rate limit | 600 cost per minute, documented in full |
| Per-endpoint costs | Published, with the paging table |
This is the section 3 rule of this directory applied honestly: where a vendor publishes no rate, we say so rather than estimating. Any figure you find for Salesloft pricing on a comparison site is somebody's quote or somebody's guess, and neither generalizes. What you can take from the table above is the shape of what Salesloft chooses to be transparent about, which is the engineering and not the commercial.
Because there is no published price, the useful planning you can do in advance is entirely technical. Work out the cost per minute your sync will consume, confirm it fits inside 600 alongside whatever else your team already has connected, and design the cursor poller rather than the pager. That work is valid whatever number comes back from the sales conversation, and it is the part that will still be true in a year.
One budget for the team, not for your integration
Salesloft API rate limits are 600 cost per minute, applied at the team level. Salesloft is explicit that having several integrated teams will not let one affect another, and equally explicit that another integration on your own team can and will affect yours.
What the scope means
Shared, and not per application.
- The 600 is per integrated team, not per integration or per API key.
- Another tool connected to the same team consumes your budget.
- Multiple integrated teams are isolated from each other.
- A team exceeding the limit because of many integrations is told to contact Salesloft rather than to optimize.
Reading your position
Two headers on every response.
- x-ratelimit-endpoint-cost reports what the request you just made cost.
- x-ratelimit-remaining-minute reports what is left in the current minute.
- Because costs can change, reading the first header is the only reliable way to know what an endpoint costs today.
- The limit can be raised by Salesloft on a customer-wide or per-team basis, which is a conversation rather than a setting.
The whole cost table points one way. Walking a list with page=1, 2, 3... is cheap for the first hundred pages and then becomes punitive, and a backfill of any size will cross that line.
Polling on updated_at and keeping a cursor costs 1 per call indefinitely, which is why Salesloft publishes a guide to it and prices the alternative at thirty times the rate. If you inherit a Salesloft integration that mysteriously exhausts its budget, look for a page parameter before anything else.
A shared team budget is the detail that decides how you build here. Your integration is not metered on its own, it is metered alongside every other one on the team, so the question is never whether your job fits in 600 cost a minute but whether it fits in whatever is left after everything else has taken its share.
How to create a Salesloft API key
Salesloft supports OAuth 2.0 for applications distributed to other teams, and an API key for a single team's own integration. The choice follows the usual line: if other companies will install it, OAuth.
Which to use
The same split as most platforms.
- An API key is the quicker route for an integration your own team owns.
- OAuth 2.0 is required for anything installed into teams you do not control.
- Either way the credential is scoped to a team, and so is the rate budget it draws on.
- The API reference at developers.salesloft.com is authoritative on the current flows.
Operational notes
What to plan for.
- Every integration on the team shares one budget, so inventory what is already connected before adding another.
- There is no documented per-key quota to isolate a noisy job.
- Rate limit increases are negotiated with Salesloft rather than configured.
- Because endpoint costs can change, treat the cost headers as the source of truth rather than a constant in your code.
OAuth is the default for anything distributed, and the scoped API key is the limited escape hatch for one team and one integration. If that is your case, the key keeps the setup to an afternoon. If there is any chance the integration gets installed elsewhere, budget the app registration before the first useful request, and do it once properly rather than per script.
Where the Salesloft API documentation lives
The Salesloft API documentation is at developers.salesloft.com and is genuinely good on the parts that matter operationally: the rate limit page carries the full cost model, the headers and the reasoning, and there is a separate guide to the polling pattern it wants you to use.
| Surface | Where | What it answers |
|---|---|---|
| Rate limits | developers.salesloft.com/docs/platform/api-basics/rate-limits | The 600 budget, the paging costs and the headers. |
| Cursor poller guide | developers.salesloft.com/docs/platform/guides | Building an efficient poller on updated_at, the pattern the costs push you toward. |
| API reference | developers.salesloft.com | Endpoints, objects and the authentication flows. |
| Integrations contact | integrations@salesloft.com | Where Salesloft sends teams that need a higher limit. |
| Pricing | salesloft.com, Talk to Sales | A form. There is no rate card. |
The documentation is worth reading even if you end up not buying, because the cost-per-minute model with published per-endpoint costs and a steep deep-paging penalty is a clean design that several vendors here would benefit from copying. It tells an integrator exactly which patterns the platform wants and prices the alternatives accordingly.
Salesloft also ships an MCP server, and it is on the MCP page with the others in this directory.
Salesloft's own product walkthrough
Salesloft publishes this on its own channel, so it is Salesloft's account of Salesloft, 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.
YouTube · Salesloft Salesloft Product Overview 2:37 · Published April 2023A positioning video rather than a product tour, and the only overview the channel offers. The customer names in it are Salesloft's own claims. Nothing in it covers the API, which is the gap this page exists to fill.
Published 7 April 2023 on Salesloft, the channel Salesloft's own pages link to, and read on 13 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 Salesloft page.
Strengths and limits
Salesloft documents the engineering unusually well and the commercials not at all.
What it does well
- The rate limit model is fully published: the budget, the per-endpoint costs and the paging table.
- Two response headers report cost and remaining budget on every call.
- Salesloft explains why deep paging is expensive and publishes the pattern it prefers instead.
- Team-level isolation means other customers cannot affect your budget.
- OAuth 2.0 for distributed apps and a simple API key for your own team.
- The limit can be raised, on a customer-wide or per-team basis.
Where it falls short
- No published price of any kind, so it cannot be compared on cost.
- No free tier and no trial figure.
- The 600 budget is shared across every integration on the team, with no per-key quota.
- Salesloft can change any endpoint's cost at any time, with no notice period documented.
- Deep paging at 30 cost will exhaust the whole budget in twenty calls.
- The MCP server is read only, in beta, and comes only with the Agent packages.
The columns are an unusually clean trade: Salesloft documents its API better than almost anyone in this directory and will not tell you what the product costs. If you are the person building the integration that is a good deal, and if you are the person signing for it, it is the whole problem.
Where Salesloft data comes from, and what you may do with it
The question that arrives late and expensively is not how good the data is, it is who is allowed to hold it. These are the fields each one returns, the coverage it claims and the compliance it publishes.
| Provider | Fields returned | Coverage | Compliance | Redistribution |
|---|---|---|---|---|
| Salesloft | CRM records, Work email, Job changes | Global | GDPR DPA SOC 2 Type II | Not stated |
None of these states a redistribution position on its pricing or docs pages. Internally that never matters. Put the rows in something your customers can see and it becomes the question your legal team asks first.
Two practical notes that apply to every provider on this page. A compliance badge describes the vendor, not your use of it, so a GDPR DPA does not give you a lawful basis for the outreach you send. And every one of these vendors runs its own opt-out, which means a person who asks you to delete their record has to be removed from your copy as well as from theirs.
If Salesloft is not the answer
Four providers in the Sending APIs listing that solve the same problem differently. Each one is a trade, and the trade is named.
Apollo
$49/seat/moSequencing, search and enrichment behind one published $49 seat, with a free plan. The obvious move when the missing rate card was the problem.
Instantly
$47/moUnlimited email accounts and warmup from $47 a month, with every price published and 100 requests a second. Built for volume rather than for enterprise process.
Smartlead
$39/moAPI-first sending infrastructure with unlimited mailboxes, if what you valued in Salesloft was throughput rather than the management layer.
HubSpot
Free tierIf the sequencer is really being bought to sit next to the CRM, HubSpot does both and includes API access on a genuinely free tier.
The full set, organized by the reason people leave, is on the Salesloft alternatives page.
Salesloft against the obvious rival
Same rate cards, read side by side, with the arithmetic done on a worked volume rather than left to you: Reply.io vs Salesloft. Every pairing in the directory is on the compare hub.
Before you build against it
Four things to settle first, each one read off Salesloft's own pages. The ticks are remembered in this browser, so you can come back to a half-finished integration.
Who should actually buy this
Salesloft is bought by sales organizations rather than by engineers, and this page is for the engineer who has been told it is happening. The good news is that the integration surface is well documented and the rate limit model is one of the clearest here. The planning you can do before any contract exists is real: size your sync in cost per minute, check it against 600 alongside the tools already connected to that team, and write a cursor poller on updated_at rather than a pager.
If you are genuinely choosing, the lack of published pricing is the thing to weigh. Nothing on salesloft.com will tell you what a seat costs, which makes a like-for-like comparison against anything else in this directory impossible without a sales call. That is a deliberate commercial choice and it is worth noticing that the same company publishes its per-endpoint API costs to the point.
The one trap to avoid: do not size the integration against today's endpoint costs as though they were fixed. Salesloft reserves the right to change them whenever it likes and says so in the documentation. Read x-ratelimit-endpoint-cost and adapt, rather than hard-coding a rate that happens to work this quarter.
For the engineer who has been handed this, the order of work is the useful takeaway. Register the OAuth app first because it gates everything, instrument the cost headers on the first real call because the budget is shared and invisible otherwise, and design the extraction around cursors rather than offsets because deep paging costs thirty times a normal request. Those three steps are most of the difference between an integration that runs quietly and one that takes the team's whole allowance at nine in the morning.
A shared budget needs somebody watching the whole team.
Six hundred cost a minute across every tool connected to one Salesloft team is an easy thing to exhaust by accident. Frontal builds the sync inside your own stack and sizes it against what you already have connected.
Worked with 300+ companies. A senior operator runs your account.
Nothing worth quoting yet
The harvest this site runs searches Reddit for Salesloft threads where the API itself is the subject, and it has not come back with a quote that survives the transcription rules yet. When one does, it lands here. Nothing on this page leans on an unquoted paraphrase.
Salesloft API, answered
Is the Salesloft API free?
No. No free tier and no published price.
How much does the Salesloft API cost?
Salesloft does not publish a price, so entry is whatever sales quotes you. Billing is per seat and subscription. Read from Salesloft's own pricing page on 8 October 2026.
What are the Salesloft API rate limits?
600 cost a minute per team. Endpoint costs vary and Salesloft can change them.
How do I get a Salesloft API key?
OAuth 2.0, or an API key for a single team. The current steps are in Salesloft's own documentation, which is authoritative on anything that has changed since 8 October 2026.
Does Salesloft have an MCP server?
Yes, at https://mcp.salesloft.com/sse. It is listed with the others on the MCP page.