Skip to main content
An error body from a matched route has a stable code, a readable message, and sometimes details. A path that matches no route gets a plain-text 404, and a method the route does not accept gets a 405 with an empty body. Match on code. See Requests and errors for the envelope, the status code table and retry rules. A code can appear with more than one status when two routes use it differently. The tables list the status each route family returns.

Authentication and access

Rate limits and caps

Request shape and size

Idempotency

Environments

Engines and versions

See Versions and releases for pin rules.

Runs

See Runs for statuses and cancellation.

Sandbox fixtures

See Sandbox fixtures.

Outcomes and annotations

See Outcomes and annotations.

Webhooks

See Webhooks.

Conversations

See Conversations and Turns and streaming for errors sent inside a stream.

Records

See Completeness and errors and Authority and scope.

Graph

Inbound events

Server errors

Last modified on September 25, 2026