Skip to main content
Every Moda API error response carries a stable code field — a machine-readable string that never changes once published. This page lists every code the API can return, along with the high-level type SDKs branch on and the HTTP status code each maps to. For the shape of the error envelope itself (type, code, message, doc_url, request_id, etc.), see Error format.

​
Branching guidance

  • Branch on type, not status code alone. Status codes collapse distinct failure modes; type separates conflict from idempotency_conflict even though both surface as 409.
  • Treat code as the narrow key. Use it for telemetry, runbook lookups, and per-error UI copy. Never display message to end users — it is developer-facing and may change.
  • Honor the envelope’s retryable field. Codes with an explicit retry contract emit retryable on every error response: false means the same request can never succeed (fix the input or state first), true means transient — retry with backoff. Where the column below shows —, retryability is context-dependent; when in doubt, retry only upstream_error and rate_limited.
  • Always log request_id. It is the single field that lets Moda support trace a specific failure across logs and Sentry.

​
Catalog

​
Type reference

The type field is a closed set. SDKs may translate types to typed exceptions; new code values may be added to an existing type without notice, so always include a default branch.