Base URL
Authentication
All endpoints require a Bearer token:Request format
- All request bodies use
Content-Type: application/json - All timestamps are ISO 8601 in UTC (e.g.,
2026-03-01T10:00:00Z) - IDs are prefixed strings:
inst_<hex>for instances,call_<hex>for calls
Response codes
| Code | Meaning |
|---|---|
200 | OK |
201 | Resource created |
204 | No content (successful delete/terminate) |
400 | Bad request — missing or invalid fields |
401 | Unauthorized — missing or invalid token |
403 | Forbidden — valid token but access denied |
404 | Resource not found |
501 | Not yet implemented |
Idempotency
If you create a call for an instance that already has an active call (QUEUED, RINGING, or IN_PROGRESS), the API returns the existing call with status 200 instead of creating a duplicate. This guards against double-submissions from network retries or React Strict Mode.