CTRLK

Error codes

|

View as Markdown

Error codes appear in message send responses and delivery reports to describe the outcome at the network level. They complement HTTP status codes and API status codes by providing a more granular reason for a delivery failure or success.

Each error is returned as a structured object with a group, an ID, a name, and a permanent flag:

json
1{
2 "groupId": 0,
3 "groupName": "OK",
4 "id": 0,
5 "name": "NO_ERROR",
6 "description": "No Error",
7 "permanent": false
8}

Error codes are organized into groups:

  • Group 0 — OK: No error. Request or delivery completed successfully.
  • Group 1 — Handset errors: Issues on the recipient's device (e.g., subscriber absent, memory full, roaming not allowed).
  • Group 2 — User errors: Problems with the request itself (e.g., invalid destination, content blocked, limit reached).
  • Group 3 — Operator errors: Network or operator-side rejections (e.g., short code not provisioned, destination blocked).

Voice, WebRTC, and push notification errors follow the same object structure with their own code ranges.

Use your browser's Ctrl+F / Command+F to search the full table by code name or ID.

For the complete error code reference, see Response status and error codes.