API usage, limits and common errors
Track your requests and active accounts, understand rate limits and quotas, and read the error codes you'll meet most.
API overview
API → API overview shows your plan and end date, your rate limits (requests per minute and trade calls per minute) and two meters: Active accounts and Registered accounts.
API usage
API usage shows requests, trade requests and peak active accounts per UTC day for the last 7, 30 or 90 days, and the busiest routes, errors and open WebSockets for the last hour, day or week. Use it to spot an app that polls too often or a spike in errors.
Errors you'll see most
401 UNAUTHORIZED— the key is missing, mistyped, revoked or expired.403 FORBIDDEN— the key lacks the permission (for example a Read key placing a trade) or the account isn't in its scope.403 QUOTA_EXCEEDED— you reached a limit, such as active or registered accounts. Deactivate or remove accounts, or move to a bigger plan.429 RATE_LIMITED— too many requests this minute. Wait the number of seconds inRetry-After, then switch from polling to webhooks or WebSocket.402 SUBSCRIPTION_EXPIRED— your plan ended; see When your plan ends.
Every error has a stable
code. Build your logic on the code, not the message, and retry only errors markedretryable.
For developers
The API side of this topic, with every field and code examples: