What you can do
- Create, update, clone, and configure voice agents
- Read call records, call details, execution history, and test-call results
- Manage campaigns, campaign workflows, contacts, and power dialer actions
- Browse voices, phone numbers, projects, and approved platform configuration
- Read billing status, usage, balances, access subscriptions, and dashboard metrics
Base URL
All REST API requests use this base URL:/api prefix in their paths. For example:
Authentication
Every public API request must include an API key as a bearer token:Response format
Successful responses use a JSON envelope:data, result, or resource-specific payload field.
Errors use the standard failure envelope:
400, 401, 403, 404, 429, and 500.
Endpoint pages list the specific success and error responses for each route.
SDKs and HTTP clients
The public API is REST over HTTPS and works with any standard HTTP client. Use the examples on each endpoint page as the source of truth for request shape, headers, and response bodies. Official SDKs are not required for launch. When SDKs are available, this page will link to setup and package documentation.Getting started
- Create an API key from the dashboard.
- Choose the minimum scopes your integration needs.
- Make a test request with the bearer token.
- Open the endpoint group you need from the sidebar.
- Use endpoint examples and error responses while building your integration.
