Rate Limits

Last updated: March 2026

The API enforces rate limits to ensure fair usage and platform stability. Limits vary by endpoint type and authentication tier.

Overview

Rate limits are applied per account and measured in requests per minute. When you exceed a limit, the API returns 429 Too Many Requests.
Your current rate limits are visible in the GET /me response under platform.rate_limits.

Default Limits

Endpoint TypeLimit
Read endpoints (GET)200 requests/minute
Write endpoints (POST, PATCH, DELETE)30 requests/minute
Authentication (POST /auth/validate-api-key)10 requests/minute
These are default values. Your specific limits may differ based on your subscription tier and can be checked via GET /me.

Handling Rate Limits

When rate limited, the API returns:
json
{
  "request_id": "...",
  "error": {
    "code": "RATE_LIMITED",
    "message": "Rate limit exceeded. Retry after 30 seconds."
  }
}
Best practices:
  1. Implement exponential backoff — wait progressively longer between retries
  2. Use bulk endpoints where available instead of many individual requests
  3. Cache responses for data that doesn't change frequently (e.g., market data, asset types)
  4. Use sparse fieldsets to reduce payload sizes and improve response times
  5. Monitor your usage via the GET /me endpoint to stay within limits