Twilio Conversations (BYOK)
Read your Twilio Conversations services, conversations, participants, roles, webhooks and push credentials with your own credentials (read-only; message text is not returned)
Read your SMSAPI account balance, sender names, contacts, blacklist, sub-users and price list with your own OAuth token
Unify Dynamics LLC
Real questions, and the tools your agent calls to answer them.
get_account_profilelist_sender_nameslist_contactslist_blacklistlist_subuserslist_pricesSMSAPI (BYOK) lets an AI assistant read your own SMSAPI data through the SMSAPI API with a key you supply (SMSAPI OAuth token). Read-only: 6 tools (get_account_profile, list_sender_names, list_contacts, list_blacklist, list_subusers, list_prices). 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 api.smsapi.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by SMSAPI. SMSAPI and its logos are trademarks of their owners and are used only to say which service the connector works with.
Sources: Live from the SMSAPI API (api.smsapi.com) with a BYOK key; documentation: https://smsapi.com/docs. Endpoints checked against that documentation on 2026-10-16.
The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.
6 tools, grouped by job. Every one is read-only or compute-only.
https://byok-smsapi.connectorbay.com/mcpThree ways in, the same 6 tools.
https://byok-smsapi.connectorbay.com/mcpPOST https://byok-smsapi.connectorbay.com/v1/tools/<tool>https://connectorbay.com/openai/byok-smsapi.jsonhttps://connectorbay.com/v1/chat/completions · how it worksX-Upstream-Key header (get one at ssl.smsapi.com).SMSAPI (BYOK) lets an AI assistant read your own SMSAPI data through the SMSAPI API with a key you supply (SMSAPI OAuth token). It is a hosted MCP server with 6 tools such as Get account profile, List sender names, List contacts, List blacklist, List subusers, List prices, published by Unify Dynamics LLC. It is independent and not affiliated with SMSAPI.
Add the MCP endpoint https://byok-smsapi.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-smsapi.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-smsapi.json.
Yes: this is a bring-your-own-key connector. Create a SMSAPI OAuth token at https://ssl.smsapi.com/react/oauth/manage and send it in the X-Upstream-Key header. ConnectorBay uses it for that one call only and never stores, logs or caches it.
Yes. Every tool reads or computes. Nothing is created, changed, sent, paid or deleted in your account.
Yes. It is free to use within the published rate limits; an optional Pro key raises them. There is no account to create.
Read your Twilio Conversations services, conversations, participants, roles, webhooks and push credentials with your own credentials (read-only; message text is not returned)
Read your Twilio Flex configuration, flex flows, plugins, plugin versions, plugin configurations and releases with your own credentials (read-only)
Read the phone numbers you own in Twilio by type, your verified caller IDs and short codes, and search numbers available to buy, with your own credentials (read-only)
Read Twilio Voice Insights call summaries, per-call quality metrics, conference summaries and video room analytics with your own credentials (read-only, no caller numbers)
Read the Twilio Marketplace add-ons you have installed and the add-ons and extensions available to install with your own credentials (read-only)
Read your Twilio Messaging Services, their senders and your A2P 10DLC brand and toll-free verification status with your own credentials (read-only; never sends a message)
https://byok-smsapi.connectorbay.com/mcpPOST https://byok-smsapi.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-smsapi.connectorbay.com/openapi.jsonX-Upstream-Key header of every request (never stored, logged or cached)https://byok-smsapi.connectorbay.com/health · Tool schemas: https://byok-smsapi.connectorbay.com/tools.jsonSMSAPI (BYOK) lets an AI assistant read your own SMSAPI data through the SMSAPI API with a key you supply (SMSAPI OAuth token). Read-only: 6 tools (get_account_profile, list_sender_names, list_contacts, list_blacklist, list_subusers, list_prices). 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 api.smsapi.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by SMSAPI. SMSAPI 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:
get_account_profile: Show the SMSAPI account name, email, username, payment type (prepaid or postpaid), user type and the number of credits (points) left.list_sender_names: List the sender names (alphanumeric senders) registered on the account with status, default flag and creation date.list_contacts: List contacts in the SMSAPI contact database with name, phone number, email, city, country, source, dates and group membership. Filter by text, phone, email, name or group; page with offset and limit.list_blacklist: List phone numbers on the account's blacklist (numbers that will not be messaged) with the date added and expiry.list_subusers: List the sub-user accounts with username, active flag, description and their credit limits.list_prices: List the current SMSAPI price list by service type, country and network, in the account currency.You bring your own SMSAPI SMSAPI OAuth token (https://ssl.smsapi.com/react/oauth/manage). 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 api.smsapi.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.
Live from the SMSAPI API (api.smsapi.com) with a BYOK key; documentation: https://smsapi.com/docs. Endpoints checked against that documentation on 2026-10-16.
Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by SMSAPI. SMSAPI 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 SMSAPI account.
Built for: Worldwide. Languages: English.
Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.
What SMSAPI (BYOK) is. SMSAPI (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own SMSAPI data: Read your SMSAPI account balance, sender names, contacts, blacklist, sub-users and price list with your own OAuth token. You bring your own SMSAPI SMSAPI OAuth token; the assistant sends it to us with each request.
BYOK key. The key you supply is used to make the one SMSAPI 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 api.smsapi.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 SMSAPI 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 SMSAPI receives. The request we make on your behalf, including the key and the arguments, under SMSAPI's own terms and privacy policy. SMSAPI acts at your direction and is the only recipient of the data of your request besides our hosting provider.
What we return. The answer SMSAPI 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 SMSAPI 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. SMSAPI (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 SMSAPI at any time to end all access.
Children. SMSAPI (BYOK) is a general-audience service operated by the adult using the assistant, under SMSAPI's own age rules.
Changes. We will post changes here with a new effective date.
Effective 24 October 2026. These terms govern use of the SMSAPI (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").
Email agent@connectorbay.com. We answer within two business days.
https://byok-smsapi.connectorbay.com/mcphttps://byok-smsapi.connectorbay.com/openapi.jsonWhen 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. SMSAPI (BYOK) never asks for them.