Rate Limits
Most public API endpoints are not rate limited today. The authenticated /v1 endpoints (conversations, leads, messaging channels, webhook subscriptions, attachment downloads, discovery) accept requests without a fixed per-key request quota.
Limited endpoints
| Endpoint | Limit |
|---|---|
POST /v1/webhooks/leads | 300 requests per minute |
GET /v1/attachments/custom-field-file-url | 60 requests per 10 minutes |
Both are keyed per company. The upload endpoint is limited on presign only, not on the confirm POST to the same path, because each presign call mints write capability against storage. See Attachments.
Exceeding a limit
When you exceed a limit, the API responds:
- Status
429 Too Many Requests - Headers:
Retry-After(seconds),X-RateLimit-Limit,X-RateLimit-Remaining - Body:
{
"error": "Too many requests. Please try again later.",
"retry_after": 42
}
If you hit 429, back off for the number of seconds in Retry-After before retrying.
note
Limits may be introduced on other endpoints in future. Build clients to handle 429 with Retry-After (exponential backoff with jitter is a good default) even where no limit applies today.