Resources
Handle errors and retries
Build predictable integrations without duplicating calls.
Inspect the whole response
Record the HTTP status, content type, and a redacted error summary. If the response is not JSON, do not attempt to parse it as JSON. Exact error envelopes and status mappings vary by service and must be confirmed for your account.
Common HTTP handling patterns
The following are general integration practices, not a promise that every A1ROUTES endpoint uses these statuses.
| Status | Suggested action |
|---|---|
| 400 | Check request parameters and required values. |
| 401 / 403 | Check the product-specific key, authentication format, and permissions. |
| 404 | Check the hostname, version, path, and access to the identifier. |
| 429 | Honor Retry-After if present; reduce request frequency. |
| 5xx | For confirmed read-only requests, retry with bounded exponential backoff and jitter. |
Treat timeouts carefully
An originate timeout does not mean the call failed. Never automatically retry a call-start request. Check the actual call state or seek support first.
Share useful diagnostics
Give support the timestamp and timezone, hostname, endpoint name, HTTP status, and a redacted request. Remove API keys, authenticated URLs, personal data, and audio before sharing logs.