Skip to content

Errors and rate limits

Limits apply at subscription level (shared by all API keys of that subscription). They are not multiplied by key count.

PlanRequests per minute
Starter10
Pro60
Business300

A custom RPM on the subscription may override the plan default when configured for Business customers.

There is no monthly request quota — usage is gated by RPM (and normal abuse protection).

Successful responses include:

  • X-RateLimit-Limit
  • X-RateLimit-Remaining
  • X-RateLimit-Reset (Unix timestamp, seconds)
HTTP/1.1 429 Too Many Requests
X-RateLimit-Limit: 10
X-RateLimit-Remaining: 0
X-RateLimit-Reset: 1710000060
Retry-After: 42
{
"code": "RATE_LIMIT_EXCEEDED",
"message": "Rate limit exceeded for this subscription."
}

Back off using Retry-After (seconds) when present.

While a subscription is past due, access continues for a 7-day grace period. After grace ends (or if billing is otherwise blocked), requests return 402 BILLING_REQUIRED until the subscription is in good standing again.

HTTPcodeWhen
400validation / bad requestInvalid query or path parameters
401UNAUTHORIZEDMissing or invalid X-API-Key
402BILLING_REQUIREDBilling state blocks access
403INSUFFICIENT_CAPABILITYEndpoint needs a higher capability tier
429RATE_LIMIT_EXCEEDEDSubscription RPM exceeded

Error bodies follow a consistent JSON shape with at least code and message. Full schemas are in the OpenAPI reference.