Errors
The API returns standard HTTP status codes with a consistent error object and requestId for support tracing.
HTTP status code summary
| Option | Type | Required | Description |
|---|---|---|---|
200 | success | - | Request completed successfully. |
202 | accepted | - | Message or campaign request accepted for processing. |
400 | bad_request | - | Missing or invalid request data. |
401 | unauthorized | - | Missing or invalid API credentials. |
402 | insufficient_balance | - | Wallet balance is not enough for this request. |
403 | insufficient_scope | - | API key does not have the required scope. |
404 | not_found | - | Resource does not exist for this workspace. |
429 | rate_limited | - | Too many requests or OTP attempts. |
5xx | server_error | - | Unexpected platform or provider error. |
Common Errors
{
"error": {
"code": "insufficient_balance",
"message": "Insufficient wallet balance."
},
"requestId": "req-123"
}Keep the requestId when contacting support. It maps to developer request logs in the API runtime.