Skip to main content

Rate Limits

Most public API endpoints are not rate limited today. The authenticated /v1 endpoints (conversations, leads, messaging channels, webhook subscriptions, attachments) accept requests without a fixed per-key request quota.

Inbound lead webhook​

One endpoint is rate limited: the inbound lead intake endpoint.

POST /v1/webhooks/leads — limited to 300 requests per minute, keyed per company (and source IP). When you exceed it, 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.