How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Twilio Conversations API

The Conversations API from Twilio — 10 operation(s) for conversations.

Twilio Conversations API is one of 115 APIs that Twilio publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.

Tagged areas include Conversations. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, pricing, and an AsyncAPI specification.

This API exposes 22 operations across 10 paths, and defines 26 schemas. It is described by OpenAPI 3.2.0, at version 1.52.0.

Requests are made against a single base URL, https://conversations.twilio.com.

22 operations 10 paths 26 schemas 4 DELETE10 GET8 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.52.0
Server
https://conversations.twilio.com
Authentication
HTTP Basic
License
Terms of Service
Resource Areas
1

Authentication & Security 1

Twilio Conversations API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (accountSid_authToken).

Paths & Operations 22

Across 10 paths, the API surfaces 22 operations — 4 DELETE, 10 GET, 8 POST. Each is listed below with its method, path, parameters, and response codes.

Conversations 22
POST
/v1/Conversations
Create a new conversation in your account's default service
CreateConversation 1 param body → 201
GET
/v1/Conversations
Retrieve a list of conversations in your account's default service
ListConversation 6 params → 200
POST
/v1/Conversations/{Sid}
Update an existing conversation in your account's default service
UpdateConversation 2 params body → 200
DELETE
/v1/Conversations/{Sid}
Remove a conversation from your account's default service
DeleteConversation 2 params → 204
GET
/v1/Conversations/{Sid}
Fetch a conversation from your account's default service
FetchConversation 1 param → 200
POST
/v1/Conversations/{ConversationSid}/Messages
Add a new message to the conversation
CreateConversationMessage 2 params body → 201
GET
/v1/Conversations/{ConversationSid}/Messages
Retrieve a list of all messages in the conversation
ListConversationMessage 5 params → 200
POST
/v1/Conversations/{ConversationSid}/Messages/{Sid}
Update an existing message in the conversation
UpdateConversationMessage 3 params body → 200
DELETE
/v1/Conversations/{ConversationSid}/Messages/{Sid}
Remove a message from the conversation
DeleteConversationMessage 3 params → 204
GET
/v1/Conversations/{ConversationSid}/Messages/{Sid}
Fetch a message from the conversation
FetchConversationMessage 2 params → 200
GET
/v1/Conversations/{ConversationSid}/Messages/{MessageSid}/Receipts/{Sid}
Fetch the delivery and read receipts of the conversation message
FetchConversationMessageReceipt 3 params → 200
GET
/v1/Conversations/{ConversationSid}/Messages/{MessageSid}/Receipts
Retrieve a list of all delivery and read receipts of the conversation message
ListConversationMessageReceipt 5 params → 200
POST
/v1/Conversations/{ConversationSid}/Participants
Add a new participant to the conversation
CreateConversationParticipant 2 params body → 201
GET
/v1/Conversations/{ConversationSid}/Participants
Retrieve a list of all participants of the conversation
ListConversationParticipant 4 params → 200
POST
/v1/Conversations/{ConversationSid}/Participants/{Sid}
Update an existing participant in the conversation
UpdateConversationParticipant 3 params body → 200
DELETE
/v1/Conversations/{ConversationSid}/Participants/{Sid}
Remove a participant from the conversation
DeleteConversationParticipant 3 params → 204
GET
/v1/Conversations/{ConversationSid}/Participants/{Sid}
Fetch a participant of the conversation
FetchConversationParticipant 2 params → 200
GET
/v1/Conversations/{ConversationSid}/Webhooks
Retrieve a list of all webhooks scoped to the conversation
ListConversationScopedWebhook 4 params → 200
POST
/v1/Conversations/{ConversationSid}/Webhooks
Create a new webhook scoped to the conversation
CreateConversationScopedWebhook 1 param body → 201
GET
/v1/Conversations/{ConversationSid}/Webhooks/{Sid}
Fetch the configuration of a conversation-scoped webhook
FetchConversationScopedWebhook 2 params → 200
POST
/v1/Conversations/{ConversationSid}/Webhooks/{Sid}
Update an existing conversation-scoped webhook
UpdateConversationScopedWebhook 2 params body → 200
DELETE
/v1/Conversations/{ConversationSid}/Webhooks/{Sid}
Remove an existing webhook scoped to the conversation
DeleteConversationScopedWebhook 2 params → 204

Schemas 26

The contract defines 26 schemas that model the data the API accepts and returns. The most detailed are conversations.v1.conversation.conversation_message (15 properties), conversations.v1.conversation (14 properties), conversations.v1.conversation.conversation_participant (12 properties), UpdateConversationRequest (11 properties). Each schema is shown below with its type and property counts.

conversations.v1.conversation.conversation_message.conversation_message_receipt
object
11 properties
conversations.v1.conversation
object
14 properties
ListConversationMessageResponse
object
2 properties
conversation_message_enum_webhook_enabled_type
string
conversation_participant_enum_webhook_enabled_type
string
conversations.v1.conversation.conversation_message
object
15 properties
conversation_message_enum_order_type
string
CreateConversationMessageRequest
object
9 properties
conversation_scoped_webhook_enum_method
string
conversations.v1.conversation.conversation_participant
object
12 properties
UpdateConversationRequest
object
11 properties
conversation_scoped_webhook_enum_target
string
conversations.v1.conversation.conversation_scoped_webhook
object
8 properties
conversation_enum_state
string
ListConversationResponse
object
2 properties
CreateConversationScopedWebhookRequest
object
7 properties 1 required
UpdateConversationMessageRequest
object
6 properties
ListConversationParticipantResponse
object
2 properties
UpdateConversationParticipantRequest
object
9 properties
ListConversationScopedWebhookResponse
object
2 properties
UpdateConversationScopedWebhookRequest
object
5 properties
CreateConversationRequest
object
11 properties
conversation_message_receipt_enum_delivery_status
string
conversation_enum_webhook_enabled_type
string
CreateConversationParticipantRequest
object
8 properties
ListConversationMessageReceiptResponse
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

twilio-conversations-api-openapi.yml Raw ↑

Other APIs Twilio publishes across the network.

Twilio A2p API
Twilio Access Tokens API
Twilio Accounts API
Twilio Alerts API
Twilio Alpha Senders API
Twilio Apps API
Twilio Archives API
Twilio Assistants API
Twilio Attempts API
Twilio Auth Tokens API
Twilio AuthTokens API
Twilio ByocTrunks API
Where this information came from

This is an independent, third-party profile of Twilio Conversations API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.