Skip to main content

Error Code Reference

Every Orbit API error response carries a machine-readable code, human-readable message, HTTP status, and contextual details. This page is generated from the canonical ERROR_CODES registry in packages/shared/src/errors.ts and lists every code in that registry — 698 in total — grouped by domain. Every code listed here is one the SDK and meta.docs_url link against. Some route handlers also return operational codes that are not yet in the registry and so are absent from the table below, so treat the code on any server response as authoritative even when it is not listed here.
HTTP status codes shown reflect the canonical status documented in the source. Some codes are reused at multiple call sites with different statuses (e.g. VALIDATION_ERROR may surface as 400 or 422); the table picks the dominant value. Treat the status field on the response envelope as authoritative for any given response.

Error Response Format

The meta.docs_url resolves to a stable per-code anchor on this page (/reference/error-codes#CODE_NAME — case-insensitive).

Authentication

Validation

Resources

Rate Limiting

Messaging

Telegram

Email (test-mode gate)

Crypto envelope

Voice

Video rooms

Agent

Agent Eval

Billing

Tenant / Multi-tenancy

System

Audit #WAVE-O-FOUNDATION — Orby

Audit #AGT-001 — confirmation-gate redemption

Audit #AGT-007 — custom-tool dispatch body cap

Audit #AGT-002 — accurate cost cap

Audit #WAVE-O-NEW-ENDPOINTS

Video / Rooms (server-side fallback codes)

Numbers / Provisioning

Compliance (DSAR / RMD / Residency / Traceback)

Campaigns / Journeys

Contacts / Imports

CDP public ingest (signed-HMAC track API)

Co-browse (live screen-share)


Handling Errors in Code

Node.js

The Devotel and DevotelApiError aliases are exported for compatibility with early-access code but Orbit / OrbitApiError are the canonical names in @devotel/orbit-sdk v0.2+.
A first-party Python SDK is on the roadmap but not yet shipped. Until then, decode the JSON response body and read meta.request_id / error.code / error.message directly from any HTTP client.
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.