Base URL
Authentication
All endpoints require an API key passed in theAuthorization header:
Request Format
- All request bodies must be JSON (
Content-Type: application/json) - All timestamps are ISO 8601 (e.g.,
2024-01-15T10:30:00Z) - Phone numbers must be in E.164 format (e.g.,
+12025550123)
Response Format
All responses follow this structure:HTTP Status Codes
| Code | Meaning |
|---|---|
200 | Success |
201 | Created |
400 | Bad Request — missing or invalid fields |
401 | Unauthorized — invalid or missing API key |
403 | Forbidden — insufficient permissions |
404 | Not Found — resource doesn’t exist |
429 | Rate Limited — too many requests |
500 | Internal Server Error |
Rate Limits
| Tier | Requests per minute |
|---|---|
| Free | 60 |
| Pro | 300 |
| Enterprise | 1,000+ (custom) |
Pagination
List endpoints support pagination:| Param | Default | Max | Description |
|---|---|---|---|
page | 1 | — | Page number |
limit | 20 | 100 | Items per page |
API Sections
Authentication
API key management and org context.
Agents
Create, update, and manage agents (Pipeline, Realtime, Text).
Voice Call Sessions
Initiate outbound calls, track sessions, get transcripts.
Text Chat API
REST + SSE text chat sessions for website chatbots.
Custom Functions
Add custom API integrations that agents call during conversations.
Webhooks
Receive real-time events when calls start, end, and more.