Help & guidesAPI & integrations › Rate limits and error codes

Rate limits and error codes

3 min read · API & integrations

Rate limits prevent API abuse. When exceeded, you will receive HTTP 429 with a Retry-After header.

Limits by plan

Trial / Standard: 60 requests / minute Pro: 300 requests / minute Business: 1000 requests / minute The limit is per-token, not per-user (you can have multiple tokens for different use cases).

Error codes

- 401 Unauthorized: missing or invalid token - 403 Forbidden: the token does not have permission for the given action (read-only token on a write endpoint) - 404 Not Found: resource does not exist - 429 Too Many Requests: rate limit exceeded, wait Retry-After seconds - 5xx: server error, retry with exponential backoff

Best practices

- Cache responses for reads (uptime data does not change every second) - Use webhooks instead of polling where possible - For batch operations, add a delay between requests