Rate limits
Each API token is rate-limited independently, on a fixed one-minute window. The limit depends on your plan:
| Plan | Requests per minute (per token) |
|---|---|
| Free | 60 |
| Solo | 600 |
| Pro | 600 |
The limit is per token, not per account — if you have multiple tokens, each gets its own allowance.
When you hit the limit
Section titled “When you hit the limit”A request that exceeds the limit gets:
HTTP/1.1 429 Too Many RequestsRetry-After: 60Retry-After tells you how many seconds to wait before the window resets. Back off for
that long, then retry — the counter resets at the start of the next one-minute window
rather than on a rolling basis.
Staying under the limit
Section titled “Staying under the limit”- Cache responses where you can, especially for data that doesn’t change every minute (e.g. the list of monitors).
- Use a separate token per integration so a noisy script doesn’t eat the budget of something that actually needs to keep up (like a status page).
- If a legitimate use case consistently needs more headroom than your plan allows, that’s a sign to upgrade rather than to retry aggressively.