Salesloft · Rate Limits

Salesloft Rate Limits

Salesloft prices the Platform API rather than counting it: every request draws from a 600-cost-per-minute budget held at the TEAM level, each endpoint has a default cost of 1, and Salesloft can change an endpoint's cost at any time without treating it as a deprecation. Deep paging is the expensive case — a request for page 501 or beyond costs 30 points, one twentieth of the whole minute. Two response headers expose the runtime signal.

Salesloft Rate Limits is the machine-readable rate-limit profile for Salesloft on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 5 rate-limit definitions, measuring cost.

The profile also includes 4 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Sales, Sales Engagement, Cadences, CRM, and Email.

5 Limits Throttle: 429
SalesSales EngagementCadencesCRMEmailRate LimitingQuotasThrottling

Limits

Team cost budget team
cost · minute
600
Applies per integrated team, not per integration. Multiple integrations on the same team share one budget and can exhaust each other's headroom. Salesloft can raise the ceiling customer-wide or per team on request to integrations@salesloft.com.
Deep paging surcharge (pages 101-150) endpoint
cost · request
3
Additional cost applied when the page parameter references index 101-150.
Deep paging surcharge (pages 151-250) endpoint
cost · request
8
Deep paging surcharge (pages 251-500) endpoint
cost · request
10
Deep paging surcharge (pages 501+) endpoint
cost · request
30
"For specific use cases, there may be a valid reason to request high page numbers, but we've found that most customers find success using a cursor poller based on the updated_at field."

Policies

Cost may change
"Salesloft is able to change the cost for an existing endpoint at any time, as the functionality doesn't become deprecated from a cost change." Costs are documented per endpoint and updates are posted to the rate-limits page.
Backoff Strategy
Read x-ratelimit-remaining-minute before issuing bursts and back off with jitter on 429. No Retry-After header is documented.
Prefer a cursor poller over deep paging
Poll on updated_at rather than incrementing page.
Request an increase
Teams exceeding the limit due to a large number of integrations should contact integrations@salesloft.com.

Sources

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/salesloft-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.