Skip to main content
Every error comes back as a non-2xx status with a single envelope: a stable machine-readable code and a human-readable message.
Branch on code in your code. It is stable across releases. The message is written for humans reading a log, and it can change at any time.

Status codes

Branching on the code

Three groups matter: what you retry, what you fix, and what you escalate.
For the retry loop these examples hand off to, see Rate limits.

Validation errors

A bad body or query parameter returns 400 bad_request with the first validation failure in message. Only the first: fix it, and the next one will surface.

Rate limits

The backoff loop for 429 and 5xx.

Authentication

Why a valid key can still return 403 forbidden.

CLI troubleshooting

The same codes, with a fix for each in the terminal.

Quickstart

Three calls, with the error branch written in.