API errors, limits and rate limits

Errors

Errors return JSON with an error code and a human-readable message.

• 401: missing or invalid key.
• 402 insufficient_credits: your balance cannot cover the call. Add funds; nothing was charged.
• 402 account_frozen: a refund or chargeback exceeded your credit. Add funds to clear the balance owed.
• 403: the key lacks the ability it needs, or the action needs a workspace that has paid (funds_required).
• 404: not found, or not in your workspace.
• 409 conflict: a section changed since you read it. Fetch it again and merge.
• 422: the request was not valid (for example a file of the wrong type or too large).
• 429: you are going too fast or have reached a daily limit. Respect the Retry-After header.

Limits

• Requests are rate limited per key; the models have their own tighter limit.
• Live-data lookups have a daily budget per workspace.
• At most three document analyses can run at once per workspace, with daily limits on analyses and on documents that could not be read.

The in-console API reference shows the exact errors for each endpoint.