This API is in beta.
Endpoints and response shapes may change before stable release.
Rate limiting
The API enforces a rolling rate limit of 100 requests per 60 seconds per integration. The limit is shared across all tokens belonging to the same account originating from the same IP address — separate integrations running from distinct servers each get their own independent window.
Response headers
Every response includes the following headers so your client can track consumption:
| Field | Type | Mutability | Notes |
|---|---|---|---|
| X-RateLimit-Limit | integer | optional | Maximum requests allowed in the window (100) |
| X-RateLimit-Remaining | integer | optional | Requests remaining in the current window |
| X-RateLimit-Reset | unix timestamp | optional | When the current window resets (seconds since epoch) |
Rate limit exceeded
When the limit is exceeded the API returns
429 Too Many Requests
with a
Retry-After
header
indicating how many seconds to wait before retrying.
429
Rate limit exceeded
{"error": "rate_limited"}
ℹ
Implement exponential backoff in your client. Rapid retries after a 429 will continue
to consume quota and extend the wait.