Be the first to get access to new connectors. Get early access →
ConnectorBay Early access

Twilio Messaging (BYOK) — connector documentation

  • MCP endpoint: https://byok-twilio-messaging.connectorbay.com/mcp
  • REST API: POST https://byok-twilio-messaging.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-twilio-messaging.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Twilio Messaging 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-Key header and the Auth Token, or the secret of the API key in X-Upstream-Key-2 of every request (never stored, logged or cached)
  • Health: https://byok-twilio-messaging.connectorbay.com/health · Tool schemas: https://byok-twilio-messaging.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-twilio-messaging · agent@connectorbay.com

What Twilio Messaging (BYOK) is for

Twilio Messaging (BYOK) lets an AI assistant read your own Twilio Messaging data through the Twilio Messaging 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 (list_messaging_services, get_messaging_service, list_service_phone_numbers, list_service_short_codes, list_service_alpha_senders, list_channel_senders, list_a2p_brand_registrations, get_a2p_brand_registration, list_brand_vettings, list_tollfree_verifications). 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 messaging.twilio.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Twilio Messaging. Twilio Messaging 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:

  • "Which Twilio Messaging Services do I have and are they A2P registered?"
  • "How is my Notifications messaging service configured?"
  • "Which phone numbers send for my Notifications messaging service?"
  • "Which short codes belong to my messaging service?"
  • "Which alphanumeric sender IDs does my messaging service use?"
  • "Which WhatsApp senders are attached to my messaging service?"

What it does

  • list_messaging_services: List the Messaging Services of the account with webhook URLs, sticky sender and smart encoding settings and A2P registration flag.
  • get_messaging_service: Get one Messaging Service: webhooks, sticky sender, smart encoding, geomatch, validity period, use case and A2P registration.
  • list_service_phone_numbers: List the phone numbers in a Messaging Service sender pool with country and capabilities.
  • list_service_short_codes: List the short codes in a Messaging Service sender pool with country and capabilities.
  • list_service_alpha_senders: List the alphanumeric sender IDs in a Messaging Service with their capabilities.
  • list_channel_senders: List the channel senders (WhatsApp, RCS and similar) attached to a Messaging Service.
  • list_a2p_brand_registrations: List your A2P 10DLC brand registrations with status, brand type, trust score and failure reason.
  • get_a2p_brand_registration: Get one A2P 10DLC brand registration: status, trust score, identity status, failure reason and entity flags.
  • list_brand_vettings: List the external vetting records (for example Aegis or Campaign Verify) of a brand registration with their status.
  • list_tollfree_verifications: List toll-free number verification requests with status and rejection reason. Business contact details are not returned.

BYOK key

You bring your own Twilio Messaging 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 messaging.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

Live from the Twilio Messaging API (messaging.twilio.com) with a BYOK key; documentation: https://www.twilio.com/docs/messaging/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 Messaging. Twilio Messaging 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 Messaging account.

Built for: Worldwide. Languages: English.