Rate Limits

Limits

Limits are tracked per API key using an in-memory sliding window. Each API server instance maintains its own counter, so actual effective limits may be slightly higher in multi-instance deployments.

Response headers

Every API response includes these headers:

X-RateLimit-Limit: 100
X-RateLimit-Remaining: 94
X-RateLimit-Reset: 1750000060

X-RateLimit-Reset is a Unix timestamp (seconds) indicating when the current window resets.

429 Too Many Requests

When you exceed the limit, the API returns:

{ "error": "Too many requests" }

with status 429. Back off for at least 60 seconds before retrying.

Best practices

• Cache list results — most data (traces, logs) doesn't change retroactively. Cache paginated responses for at least 30 seconds.
• Use TQL for aggregations — a single TQL query that returns aggregated rows is far more efficient than fetching 500 raw traces to compute a count client-side.
• Prefer webhooks for real-time — if you need to react to incidents as they happen, webhooks are more efficient than polling the incidents endpoint.