Twilio Notify (BYOK)

Twilio Notify (BYOK) — connector documentation

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

What Twilio Notify (BYOK) is for

Twilio Notify (BYOK) lets an AI assistant read your own Twilio Notify data through the Twilio Notify 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: 5 tools (list_services, get_service, list_credentials, get_credential, list_bindings). 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 notify.twilio.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Twilio Notify. Twilio Notify 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 Notify services do I have?"
• "How is Notify service IS... configured?"
• "Which push credentials are stored in Twilio Notify?"
• "What type of push credential is CR?"
• "How many devices are registered in Notify service IS?"

What it does

• list_services: List Notify Services with friendly name, linked push credentials, messaging service and whether logging is enabled.
• get_service: Get one Notify Service: friendly name, push credential SIDs, default protocol versions, log and delivery callback flags.
• list_credentials: List push credentials (APN, FCM or GCM) stored in Notify with name, type and sandbox flag. The secret values are never returned.
• get_credential: Get one push credential's name, type (apn, gcm or fcm) and sandbox flag.
• list_bindings: List the devices registered for a Notify Service by channel type, protocol version and tags. The device address and user identity are not returned.

BYOK key

You bring your own Twilio Notify 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 notify.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/notify/api (the API this connector calls, with a BYOK key)

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

Built for: Worldwide. Languages: English.

Twilio Notify (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Twilio Notify (BYOK) is. Twilio Notify (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Twilio Notify data: Read your Twilio Notify push notification services, push credentials and binding counts per channel type with your own credentials (read-only). You bring your own Twilio Notify Account SID or API key SID (use a restricted API key, SID starts with SK, rather than the main Auth Token where possible); the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Twilio Notify call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to notify.twilio.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Twilio Notify rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What Twilio Notify receives. The request we make on your behalf, including the key and the arguments, under Twilio Notify's own terms and privacy policy. Twilio Notify acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Twilio Notify gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your Twilio Notify data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. Twilio Notify (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at Twilio Notify at any time to end all access.

Children. Twilio Notify (BYOK) is a general-audience service operated by the adult using the assistant, under Twilio Notify's own age rules.

Changes. We will post changes here with a new effective date.

Twilio Notify (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the Twilio Notify (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. Twilio Notify (BYOK) provides: Read your Twilio Notify push notification services, push credentials and binding counts per channel type with your own credentials (read-only). It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
2. Your own key, your own account. You must use your own Twilio Notify credentials and only access data you are allowed to access. Twilio Notify's terms apply to your use of Twilio Notify; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Twilio Notify. Twilio Notify and its logos are trademarks of their owners and are used only to say which service the connector works with.
4. No advice, no guarantees. Output is the data Twilio Notify returns, lightly trimmed; it may be incomplete, delayed or changed by Twilio Notify. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Twilio Notify account.
6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent Twilio Notify's controls, or to attack any system.
7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; Twilio Notify may change or end its API at any time.
8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your Twilio Notify key.
10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action Twilio Notify takes on your account. Our total liability is limited to US $100.
11. Governing law. California law; venue in San Mateo County, California.
12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-twilio-notify

Twilio Notify (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://byok-twilio-notify.connectorbay.com/mcp
• REST API: https://byok-twilio-notify.connectorbay.com/openapi.json
• Live status: https://byok-twilio-notify.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Twilio Notify (BYOK) never asks for them.