Skip to main content
The Talkturo REST API gives you full programmatic control over your Voice AI infrastructure. You can create and configure AI assistants, build and launch outbound campaigns, manage your CRM contacts and companies, purchase phone numbers, and retrieve call data — all without touching the dashboard. Every action available in the Talkturo web app is backed by this API.

Authentication

Learn how to get your API token and authorize requests.

Assistants

Create, configure, and assign phone numbers to AI assistants.

Campaigns

Build outbound campaigns and start batch calling.

Contacts

Create and list CRM contacts for your campaigns.

Companies

Manage company records and associate contacts.

Phone Numbers

Search, purchase, and list phone numbers.

Webhooks

Receive real-time events for calls and billing.

​
Base URL

All API endpoints are relative to your Talkturo account domain: 
https://<your-domain>/api
For example, to list campaigns, you send a request to: 
https://<your-domain>/api/crm/campaigns

​
Request format

Send all request bodies as JSON and include the Content-Type: application/json header on every POST and PATCH request. 
curl -X POST https://<your-domain>/api/assistants \
  -H "Authorization: Bearer <token>" \
  -H "Content-Type: application/json" \
  -d '{"accountSlug": "my-team", "name": "Sales Agent"}'

​
Response format

Every response returns a JSON object with a top-level success boolean. On success, the response includes the relevant resource object or array. On failure, it returns an appropriate HTTP status code and a message describing the error. 
{
  "success": true,
  "assistant": {
    "id": "asst_01j...",
    "name": "Sales Agent",
    ...
  }
}
Paginated list endpoints also return count, limit, and offset fields alongside the data array: 
{
  "success": true,
  "campaigns": [...],
  "count": 120,
  "limit": 50,
  "offset": 0
}

​
HTTP status codes

CodeMeaning
200Request succeeded
400Invalid or missing request parameters
401Missing or invalid authentication token
403Authenticated but not authorized for this action
404The requested resource does not exist
409Conflict — the resource already exists
500Internal server error

​
Authentication

All endpoints require a Bearer token in the Authorization header. See the authentication guide for details on how to obtain and use your token.