API reference
Rate limits
Two limits apply to every API-key request. The tier daily cap is the ceiling; per-key limits can only tighten it, never raise it. Exceeding either returns 429.
1 · Tier daily cap
A per-organisation daily request budget set by your subscription tier. Shared across all of your keys and browser sessions.
2 · Per-key buckets
Optional minute / hour / day limits set per key. A null limit disables that window. Useful to stop one integration from burning the whole org's daily budget.
- Per minute: short-burst protection
- Per hour: sustained-rate protection
- Per day: per-integration daily sub-budget (≤ tier cap)
Response headers
API-key responses carry the remaining budget for each active window:
| Header | Meaning |
|---|---|
| X-RateLimit-Limit-Minute | Per-minute cap for this key |
| X-RateLimit-Remaining-Minute | Requests left in the current minute |
| X-RateLimit-Reset-Minute | Seconds until the minute window resets |
| X-RateLimit-Limit-Hour / -Day | Hour / day caps (same shape) |
| X-RateLimit-Remaining-Hour / -Day | Requests left in hour / day |
| Retry-After | On 429: seconds to wait before retrying |
Handling 429
On 429 the body is the standard error envelope with code: "RATE_LIMITED". Respect Retry-After and back off; the Remaining headers let you self-throttle before you hit the wall.