Twilio Conversations (BYOK) — connector documentation
- MCP endpoint:
https://byok-twilio-conversations.connectorbay.com/mcp - REST API:
POST https://byok-twilio-conversations.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec athttps://byok-twilio-conversations.connectorbay.com/openapi.json - Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
- Authentication: your own Twilio Conversations Account SID or API key SID (use a restricted API key, SID starts with SK, rather than the main Auth Token where possible), sent in the
X-Upstream-Keyheader and the Auth Token, or the secret of the API key inX-Upstream-Key-2of every request (never stored, logged or cached) - Health:
https://byok-twilio-conversations.connectorbay.com/health· Tool schemas:https://byok-twilio-conversations.connectorbay.com/tools.json - Publisher: Unify Dynamics LLC · connectorbay.com/byok-twilio-conversations · agent@connectorbay.com
What Twilio Conversations (BYOK) is for
Twilio Conversations (BYOK) lets an AI assistant read your own Twilio Conversations data through the Twilio Conversations API with a key you supply (Account SID or API key SID (use a restricted API key, SID starts with SK, rather than the main Auth Token where possible)). Read-only: 10 tools (get_global_configuration, list_services, list_conversations, get_conversation, list_service_conversations, list_participants, list_roles, list_conversation_webhooks, list_push_credentials, list_address_configurations). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to conversations.twilio.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Twilio Conversations. Twilio Conversations and its logos are trademarks of their owners and are used only to say which service the connector works with.
Ask your assistant things like:
- "What are my default Twilio Conversations settings?"
- "Which Twilio Conversations services do I have?"
- "Which Twilio conversations are currently active?"
- "What is the state of Twilio conversation CHaaa...?"
- "Which closed conversations does my second Conversations service have?"
- "Who takes part in Twilio conversation CHaaa...?"
What it does
get_global_configuration: Show the account-wide Conversations settings: default service, default messaging service and the default inactivity and closing timers.list_services: List the Conversations services of the account.list_conversations: List conversations in the default service with state and dates, optionally filtered by state and creation time. Message text is not returned.get_conversation: Get one conversation from the default service: names, state, linked services and timestamps.list_service_conversations: List conversations of one specific Conversations service, optionally filtered by state and creation time.list_participants: List the participants of a conversation: identity, role and last-read position. Phone numbers and addresses of the participants are not returned.list_roles: List the user roles of the default service with their type (conversation or service) and permission names.list_conversation_webhooks: List the webhooks scoped to one conversation: target type and URL.list_push_credentials: List push notification credentials (FCM or APNs) registered for Conversations: name, type and sandbox flag. Secrets are not returned.list_address_configurations: List the address configurations that route SMS, WhatsApp or other channel addresses into Conversations.
BYOK key
You bring your own Twilio Conversations Account SID or API key SID (use a restricted API key, SID starts with SK, rather than the main Auth Token where possible) (https://www.twilio.com/docs/iam/api-keys/keys-in-console). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to conversations.twilio.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.
Data sources
- https://www.twilio.com/docs/conversations/api (the API this connector calls, with a BYOK key)
Live from the Twilio Conversations API (conversations.twilio.com) with a BYOK key; documentation: https://www.twilio.com/docs/conversations/api. Endpoints checked against that documentation on 2026-10-16.
What it is not
Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Twilio Conversations. Twilio Conversations and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Twilio Conversations account.
Built for: Worldwide. Languages: English.