Skip to main content
API responses may include a numeric code, a status string (UPPER_SNAKE_CASE), and a human-readable description. Use this page to interpret errors and handle them in your application.
Error responses typically include code, status, and description. The status field is stable for programmatic handling; the description may be updated for clarity.

General (90001–90099)

Validation (90100–90199)

System (90200–90299)

Pricing (90400–90499)

WhatsApp (90500–90699)

General & template

Message payload & body

Interactive messages

RCS (90700–90899)

SMS (90900–91999)

SMS errors are grouped by category. Ranges: 90900–90999 API-facing shared codes; 91000–91064 validation, DLT, and template/content; 91400–91999 delivery, operator, handset, user, and provider. Delivery reports and vendor responses may map to these internal codes.

SMS general (90900–91099)

Code 90903 is reserved as a legacy slot and documented below as SMS_CODE_RESERVED.

SMS DLT (91006–91056)

DLT (Do Not Disturb / regulatory) codes apply to SMS in India. Vendor delivery reports may map to these internal codes.

SMS template/content (91057–91064)

SMS delivery (91400–91499)

SMS operator (91500–91599)

A few operator statuses are vendor-provided legacy values and may not strictly follow modern SNAKE_CASE formatting.

SMS handset/subscriber (91600–91699)

SMS user/account (91700–91799)

Some statuses in this section are vendor-derived and preserved as-is for backward compatibility (including legacy spellings).

SMS provider (91800–91899)

Provider statuses in this range are protocol-level and vendor-derived. Use the status value for precise diagnosis; descriptions are normalized summaries.

Email (91100–91299)

Reserved for the email channel. The following codes are defined today: