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

Twilio Messaging Compliance (BYOK) — connector documentation

  • MCP endpoint: https://byok-twilio-messaging-compliance.connectorbay.com/mcp
  • REST API: POST https://byok-twilio-messaging-compliance.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-twilio-messaging-compliance.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Twilio Messaging Compliance 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-compliance.connectorbay.com/health · Tool schemas: https://byok-twilio-messaging-compliance.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-twilio-messaging-compliance · agent@connectorbay.com

What Twilio Messaging Compliance (BYOK) is for

Twilio Messaging Compliance (BYOK) lets an AI assistant read your own Twilio Messaging Compliance data through the Twilio Messaging Compliance 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: 9 tools (list_a2p_campaigns, get_a2p_campaign, list_service_a2p_usecases, list_us_a2p_usecases, get_domain_config, get_service_domain_config, get_service_domain, validate_domain_dns, get_domain_certificate). 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 Compliance. Twilio Messaging Compliance 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 is the status of the A2P campaign for my Twilio messaging service?"
  • "Was Twilio A2P campaign QE... approved?"
  • "Which A2P use cases can my Twilio messaging service register?"
  • "What US A2P use case codes does Twilio support?"
  • "How is link shortening configured for my Twilio domain?"
  • "Which link shortening config does my Twilio messaging service use?"

What it does

  • list_a2p_campaigns: List the US A2P 10DLC campaign registrations of a Messaging Service with brand, use case, status (for example IN_PROGRESS, VERIFIED, FAILED) and opt-in and opt-out keywords. Sample messages are not returned.
  • get_a2p_campaign: Get one US A2P campaign registration by SID: brand, use case, status, content flags and keywords (sample messages are not returned).
  • list_service_a2p_usecases: List the US A2P use cases a Messaging Service can register a campaign for, optionally for one brand registration.
  • list_us_a2p_usecases: List all use cases that exist for US A2P messaging registrations.
  • get_domain_config: Get the link shortening settings of a branded domain: callback URL, fallback URL, whether to continue when shortening fails and the HTTPS setting.
  • get_service_domain_config: Get the link shortening settings that apply to a Messaging Service: its domain, callback URL, fallback URL and failure handling.
  • get_service_domain: Get the link shortening domain SID attached to a Messaging Service.
  • validate_domain_dns: Check whether the DNS records of a link shortening domain are valid, with the reason when they are not. Read only; changes nothing.
  • get_domain_certificate: Get the TLS certificate record of a link shortening domain: domain name, certificate SID and creation, update and expiry dates.

BYOK key

You bring your own Twilio Messaging Compliance 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 Compliance API (messaging.twilio.com) with a BYOK key; documentation: https://www.twilio.com/docs/messaging/api/linkshortening-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 Compliance. Twilio Messaging Compliance 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 Compliance account.

Built for: Worldwide. Languages: English.