Close · Rate Limits

Close Rate Limits

Close enforces per-endpoint-group rate limits. Each endpoint group (different URL paths and HTTP methods) has its own bucket. Limits at the organization level are 3x the per-API-key limits. Some endpoints carry stricter unpredictable limits in addition to the documented bucket.

Close Rate Limits is the machine-readable rate-limit profile for Close on the APIs.io network, in the API Commons Rate Limits shape.

It captures 4 rate-limit definitions, measuring requests and events.

Limit state is signalled in the primary, retry_after, deprecated, and body response headers, and an exhausted limit returns HTTP 429.

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

Tagged areas include CRM, Sales Engagement, Rate Limiting, and Throttling.

4 Limits Exhausted: HTTP 429 primaryretry_afterdeprecatedbody
Transcribed from the provider's documentation on 2026-08-13 — developer.close.com/api/overview/rate-limits.
View Source
CRMSales EngagementRate LimitingThrottling

Limits

Per API Key Per Endpoint Group token
requests
Each endpoint group (path + method combination) has its own per-API-key bucket. Inspect the `RateLimit` response header for live limit / remaining / reset values.
Per Organization organization
requests
Organization-level limit is 3x the per-API-key limit, allowing multiple keys in the same org to share headroom.
Hidden Tighter Limits endpoint
requests
Some endpoints have tighter unpredictable limits that may trigger 429 even within the documented window; rely on response headers rather than precomputed budgets.
Webhook Delivery subscription
events
Outbound deliveries are retried with exponential backoff up to every 20 minutes, for up to 72 hours, then dropped. A subscription is paused automatically at a 100,000-event backlog or after 3 days of total delivery failure. Maximum 40 subscriptions per organization (500 for Zapier, Backendless, Integrately and Customer.io Journeys). See asyncapi/close-webhooks.yml.

Policies

Backoff Strategy
On 429, sleep for the number of seconds specified in the `RateLimit` reset value (preferred) or the `Retry-After` header.
Header Telemetry
Track the `RateLimit` header (limit / remaining / reset) on every response and slow down proactively as remaining drops.
Spread Across Keys
Use multiple API keys per organization to spread load; the org- level bucket is 3x the per-key bucket.

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/close-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 form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

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