Error Handling
Modified on: 2026-03-12 10:43
All API response errors are handled in a consistent and unified way, regardless of the type of operation being performed. Whether it's a call request, a call result, or a call cancellation, the error response follows the same structure and format.
This uniform approach allows developers to implement a single error-handling strategy across all endpoints, reducing complexity and making integrations easier to maintain.
Error Format
| Level | Field Name | Num.Occ. | Data Type | Format | Description | Example |
|---|---|---|---|---|---|---|
| 1 | error | 0..1 | object | - | Object used for error description | - |
| 2 | code | 1 | String | 100 Char | Short error description | BAD_REQUEST |
| 2 | message | 1 | String | 500 Char | Long error description | "Invalid request: call type cannot be empty" |
Error Example
{
"error": {
"code": "BAD_REQUEST",
"message": "Invalid call type: BOOKING_VERIFIC"
},
"success": false
}
Did you find it helpful? Yes No
Send feedback