Skip to contentSkip to navigationSkip to topbar
On this page

Conversational Intelligence API Overview


The Conversational Intelligence API allows you to analyze and extract actionable business intelligence from conversations between your customers and agents using artificial intelligence and machine learning technologies.

This REST API lets you start conversation analysis services, generate transcripts, and manage webhooks that send information to your application while Intelligence Services extracts meaningful data.


Base URL for API

base-url-for-api page anchor

All endpoints in the Conversational Intelligence API reference documentation use the following base URL:

https://intelligence.twilio.com/v2

The API is served over HTTPS. To ensure data privacy, it doesn't support unencrypted HTTP. It provides all responses in JSON format.


The Conversational Intelligence API includes these resources:

Service resource

  • Service resource: Create, initialize, and manage Intelligence Services.
  • OperatorAttachment subresource: Create and delete Operator Attachments from a Service.
  • OperatorAttachments subresource: Fetch Operator Attachments associated with a Service.

Transcript resource

Operator resource

OperatorType resource


Authenticate API requests

authenticate-api-requests page anchor

To authenticate requests to the Twilio APIs, Twilio supports HTTP Basic authentication(link takes you to an external page). Use your API key as the username and your API key's secret as the password. You can create an API key either in the Twilio Console or using the API.

Note: Twilio doesn't recommend using your Account SID and Auth Token in production. For local testing, you can use your Account SID as the username and your Auth token as the password. You can find your Account SID and Auth Token in the Twilio Console(link takes you to an external page).

Learn more about Twilio API authentication.

Restricted API keys

restricted-api-keys page anchor

You can use Restricted API keys with Conversational Intelligence for fine-grained control over API resources. For example, you can provide permissions for an API key to only modify Intelligence Service resources, but not access potentially-sensitive information such as unredacted Transcript Media subresources, Transcript resources, or Transcript OperatorResults subresources.

For more information on Twilio's REST API, refer to the Usage documentation on sending requests, API responses, and security.


Conversational Intelligence API endpoints are rate limited. You should follow the REST API Best Practices, and implement retries with exponential backoff to properly handle the API response Error 429 "Too Many Requests"(link takes you to an external page) for high-volume workloads.