Error Codes
For the full error-code reference — every code in the canonical
error-code registry, grouped by domain — see the Error Code Reference
page. The table below is a focused subset of the codes developers
encounter most during integration.
Common Error Codes
Handling errors in code
Every endpoint — messages, voice, contacts, agents — returns errors in
the error envelope above. It is a platform concern, not tied to one
endpoint: a Python client and a Go client see the same code /
message / status / meta.request_id as a Node client, and the
language SDKs mirror that shape so code always indexes into the
table above.
Node.js — retrying 429 with backoff
Python
The Python SDK subclasses OrbitError per HTTP class —
OrbitAuthenticationError (401/403), OrbitRateLimitError (429,
carries retry_after), OrbitClientError (other 4xx), and
OrbitServerError (5xx) — so catch a subclass when you want the
specific class. OrbitError itself catches every API failure.
Java, C#, PHP, Ruby
The Java, C#, PHP, and Ruby SDKs are not yet published to their package
registries, so the registry blocks below describe the future registry
shape. Until first registry publication, do a plain HTTP call — the
JSON envelope is the same, so a request read of error.code /
meta.request_id plus a Retry-After header is all the SDK would
do anyway.
Always include the request_id from the error response meta
when contacting Orbit support. This allows us to trace the exact
request through our infrastructure.
For the complete list of error codes — including messaging, voice,
AI-agent, billing, compliance, and system errors — see the
Error Code Reference.