canonical: https://jentic.com/apis/twilio.com/twilio---conversations # Twilio - Conversations This is the public Twilio REST API. The API exposes 103 endpoints secured with basic authentication. ## For AI agents Programmatically update the global configuration of conversations on your account, fetch the global configuration of conversations on your account. Covers 103 operations with basic authentication. ## Scope Does not handle payments, crm, or developer tools - use for communications only. ## Capabilities - Update the global configuration of conversations on your account - Fetch the global configuration of conversations on your account - Create a new address configuration - Retrieve a list of address configurations for an account - Remove an existing address configuration ## Use cases ### Communications Operations Use the Twilio - Conversations to perform communications operations programmatically. The API provides 103 endpoints covering core functionality including update the global configuration of conversations on your account, fetch the global configuration of conversations on your account, create a new address configuration. Example prompt: Call POST /v1/Configuration to update the global configuration of conversations on your account ### Automated ConversationsV1AddressConfiguration Management Automate conversationsv1addressconfiguration operations by combining multiple Twilio - Conversations endpoints. Agents can fetch the global configuration of conversations on your account and then create a new address configuration in a single workflow. Example prompt: Call GET /v1/Configuration to fetch the global configuration of conversations on your account, then verify the result ### AI Agent Integration via Jentic AI agents discover and call Twilio - Conversations endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle basic tokens manually. Example prompt: Search Jentic for 'update the global configuration of conversations on your account', load the operation schema, and execute with Jentic-managed credentials ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | /v1/Configuration | Update the global configuration of conversations on your account | | GET | /v1/Configuration | Fetch the global configuration of conversations on your account | | POST | /v1/Configuration/Addresses | Create a new address configuration | | GET | /v1/Configuration/Addresses | Retrieve a list of address configurations for an account | | POST | /v1/Configuration/Addresses/{Sid} | Update an existing address configuration | | GET | /v1/Configuration/Addresses/{Sid} | Fetch an address configuration | | DELETE | /v1/Configuration/Addresses/{Sid} | Remove an existing address configuration | | POST | /v1/Conversations | Create a new conversation in your account's default service | ## Key resources - **ConversationsV1AddressConfiguration** — Operations related to ConversationsV1AddressConfiguration - **ConversationsV1Binding** — Operations related to ConversationsV1Binding - **ConversationsV1ChannelMetadata** — Operations related to ConversationsV1ChannelMetadata - **ConversationsV1Configuration** — Operations related to ConversationsV1Configuration - **ConversationsV1Conversation** — Operations related to ConversationsV1Conversation ## Why Jentic - **Setup:** Wiring Twilio Conversations by hand means setting up HTTP basic auth with your Account SID and Auth Token, pointing at the conversations.twilio.com host, and handling pagination and retries across its many configuration and conversation operations yourself. Through Jentic you install once, import Twilio Conversations from the API Directory, store the Account SID and Auth Token once, and your agent calls it. - **Permission scoping:** Twilio Conversations puts resource ids like the address id in the URL path (/v1/Configuration/Addresses/{Sid}), so a rule can pin your agent to one address: it can read or update that address and nothing else. You choose the operations it may call, so destructive ones like deleting an address are not included unless you add them. - **Credential handling:** Your Twilio Account SID and Auth Token are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'update the global configuration of conversations on your account', and Jentic returns the matching Twilio Conversations operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Sendgrid** — Alternative communications API - **Pusher** — Alternative communications API ## FAQ ### What authentication does the Twilio - Conversations use? The Twilio - Conversations uses HTTP Basic authentication with username and password. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context. ### Can I update the global configuration of conversations on your account with the Twilio - Conversations? Yes. Use the POST /v1/Configuration endpoint. The API returns structured JSON responses that agents can parse and act on directly. ### What are the rate limits for the Twilio - Conversations? Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer. ### How do I update the global configuration of conversations on your account through Jentic? Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'update the global configuration of conversations on your account'. Jentic returns the matching Twilio - Conversations operation with its input schema. Load the schema and execute the call - credentials are injected automatically. ### How many endpoints does the Twilio - Conversations have? The Twilio - Conversations exposes 103 endpoints covering conversationsv1addressconfiguration, conversationsv1binding, conversationsv1channelmetadata operations. ### Can I limit what my agent is allowed to do with the Twilio Conversations API? Yes. Because you run Jentic One yourself, your own rules decide which Twilio Conversations operations and credentials the agent can use. Since resource ids like the address id sit in the URL path (/v1/Configuration/Addresses/{Sid}), a rule can pin the agent to a single address so it can only fetch or update that one and nothing else. You also pick the operations it may call, so destructive ones such as DELETE /v1/Configuration/Addresses/{Sid} are excluded unless you add them.