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.
4 Limits
Throttle: 429
CRMSales EngagementRate LimitingThrottling
Limits
Per API Key Per Endpoint Group token
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
Organization-level limit is 3x the per-API-key limit, allowing multiple keys in the same org to share headroom.
Hidden Tighter Limits endpoint
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
Webhooks include HMAC signatures and are retried on 5xx; receivers should respond 2xx within the platform timeout.
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.