ResourcesReference

API rate limits

Learn about rate limits for Respan API endpoints and how to handle them.

Ask for help?

We are still updating our rate limit plan. Rate limits are subject to change as we adjust limits based on usage patterns and platform capacity.

  • Join our Discord community — Get help from the community and our team
  • Request a demo — Contact us for better customer support and to discuss your specific needs

Basics rate limits

We apply per-endpoint rate limits to protect the platform and ensure fair usage across all organizations.

Endpoint CategoryRate LimitScope
Bulk trace deletion (POST /api/traces/bulk/)10 requests/minute; up to 1,000 matching traces/requestPer organization and exact endpoint path for API-key calls (shared across all API keys); per user and exact endpoint path for JWT calls
Bulk spans (POST /api/request-logs/bulk/)30 requests/minute; up to 500 spans/requestPer organization and exact endpoint path for API-key calls (shared across all API keys); per user and exact endpoint path for JWT calls
Bulk dataset logs (POST /api/datasets/{dataset_id}/logs/bulk/)30 requests/minute; up to 500 logs/requestPer organization and dataset-specific endpoint path for API-key calls (shared across all API keys); per user and dataset-specific endpoint path for JWT calls
Bulk cache deletion (DELETE /api/caches/bulk/)60 requests/minute; up to 1,000 cache keys or IDs/requestPer organization and exact endpoint path for API-key calls (shared across all API keys); per user and exact endpoint path for JWT calls
Users API60 requests/minutePer organization
Other APIs (excluding Logs & Gateway)60 requests/minutePer organization

When Limits Are Exceeded

When you exceed the rate limit, you’ll receive an HTTP 429 Too Many Requests response:

1{
2  "detail": "Rate limit exceeded",
3  "retry_after": 30
4}

The retry_after field indicates the number of seconds you should wait before retrying.