Errors and request IDs
Handle public error envelopes and retain request identifiers for diagnosis.
JSON errors use this envelope:
{
"statusCode": 400,
"message": "page must be a positive integer",
"error": "Bad Request"
}error can be omitted.
| Status | Meaning | Retry? |
|---|---|---|
400 | Invalid or missing parameter | Fix request |
401 | Missing or invalid API key | Fix key |
404 | Requested prospect, call, or recording does not exist | Usually no |
416 | Recording byte range cannot be satisfied | Use valid range |
429 | Rate limit exceeded | Honor Retry-After |
500 | Unexpected Sonik error | Retry with backoff |
502 | Recording provider failed | Retry with backoff |
Every public data response includes:
Cache-Control: private, no-store
x-correlation-id: backend-example-id
x-request-id: request-example-idCapture both request identifiers when diagnosing failures. Cache header prevents browsers and intermediaries from storing workspace data.
Updated 9 days ago
Did this page help you?
