Skip to main content
When a request fails, the API answers with an HTTP status code and a JSON body that says why. Use the status code to decide what your program does next, and show or log the detail.

The error body

detail is usually a sentence. A few answers differ:

Status codes

Messages you may see

Starting a run

Account and usage (SaaS)

On Business, the spend limit in that last message is the member’s top-up limit: how much of the organization’s top-ups one member may use per billing period. A 429 for usage has no Retry-After: it does not clear by waiting a few seconds.

Usage limits (Enterprise)

By default, POST /chat with an API key on Enterprise is not checked against usage limits and budgets; your deployment can turn that check on. Starting a workflow run is always checked, for keys too. A run past a limit answers 429 with one of these: An Admin’s key reads … Raise it on Spend limits. instead of the last sentence.

Pauses and follow-ups