API Overview

{
  "success": true,
  "data": {
    "id": "ast_9f3d2c11",
    "name": "Inbound Support Assistant"
  }
}

{
  "success": false,
  "error": "Unauthorized"
}

Build on the Talkturo API

Build integrations and automations on top of Talkturo's voice AI platform with a REST API for assistants, telephony, phone numbers, credits, CRM data, workflows, and account management. Use this page to understand the API's core conventions and find the endpoint group you need.

Authenticate requests

Talkturo supports three authentication methods. Most external integrations should use API keys, while browser and desktop clients use platform-specific authentication flows.

Understand the response format

Most endpoints return JSON in a consistent envelope so you can handle success and failure predictably across the API. Successful responses return a success flag and response data, while failed responses return a success flag and error details.

Handle HTTP status codes

Talkturo uses standard HTTP status codes in addition to the JSON response body. Check the status code first, then inspect the response envelope for details your application can log or surface.

Plan for rate limits

API keys are limited to 1000 requests per hour by default. If you build background jobs, retries, or bulk syncs, add backoff and retry handling so your integration degrades gracefully when it reaches the limit.

Browse endpoint groups

Start with the group that matches the resource or workflow you need to integrate. Each reference page documents endpoints, authentication requirements, and request or response details for that area of the API.

Start with the most common integration path

Most external developers begin with API keys, then move into assistants, telephony, or CRM endpoints depending on the product they are building. If you are setting up a new integration, read Authentication first, then continue to the resource-specific reference page for your use case.