SignalWire (BYOK)

SignalWire (BYOK) — connector documentation

• MCP endpoint: https://byok-signalwire.connectorbay.com/mcp
• REST API: POST https://byok-signalwire.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-signalwire.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: your own SignalWire SignalWire Project ID, sent in the X-Upstream-Key header and the SignalWire API token (needs the Numbers scope for number reads) in X-Upstream-Key-2 of every request (never stored, logged or cached)
• Health: https://byok-signalwire.connectorbay.com/health · Tool schemas: https://byok-signalwire.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/byok-signalwire · agent@connectorbay.com

What SignalWire (BYOK) is for

SignalWire (BYOK) lets an AI assistant read your own SignalWire data through the SignalWire API with a key you supply (SignalWire Project ID). Read-only: 9 tools (list_phone_numbers, list_short_codes, list_number_groups, list_domain_applications, list_queues, list_video_rooms, list_messaging_brands, list_brand_campaigns, list_fabric_resources). 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 *.signalwire.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by SignalWire. SignalWire 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 phone numbers do we own in SignalWire?"
• "What short codes does our SignalWire project have?"
• "What number groups are set up in SignalWire?"
• "Which SIP domain applications exist in SignalWire?"
• "How long is the wait in our SignalWire call queues?"
• "What video rooms are configured in SignalWire?"

What it does

• list_phone_numbers: List the phone numbers owned by the project with capabilities, type, E911 status, caller ID name, next billing date and call handler. Needs the Numbers scope.
• list_short_codes: List the project's SMS short codes with capabilities, country, code type, lease duration and next billing date.
• list_number_groups: List number groups (pools used to pick a sender) with sticky-sender flag and phone number count.
• list_domain_applications: List SIP domain applications with domain, name, identifier, IP-auth flag and call handler (the IP allow-list itself is left out).
• list_queues: List call queues with maximum size, current size and average wait time in seconds.
• list_video_rooms: List video rooms with name, maximum members, quality, layout and join window.
• list_messaging_brands: List 10DLC messaging registry brands with name, legal company name, state, legal entity type and vertical (tax id and contacts are left out).
• list_brand_campaigns: List the messaging campaigns registered under one brand with name, state and SMS use case.
• list_fabric_resources: List Call Fabric resources (AI agents, call flows, SWML scripts and similar) with display name, type and dates.

BYOK key

You bring your own SignalWire SignalWire Project ID (https://signalwire.com/docs/platform/your-signalwire-api-space). 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 *.signalwire.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://signalwire.com/docs/apis (the API this connector calls, with a BYOK key)

Live from the SignalWire API (*.signalwire.com) with a BYOK key; documentation: https://signalwire.com/docs/apis. 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 SignalWire. SignalWire 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 SignalWire account.

Built for: Worldwide. Languages: English.

SignalWire (BYOK) — Privacy Policy

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

What SignalWire (BYOK) is. SignalWire (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own SignalWire data: Read your SignalWire project setup: phone numbers, short codes, number groups, queues, video rooms and messaging registry brands with your own Project ID and API token. You bring your own SignalWire SignalWire Project ID; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one SignalWire 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 *.signalwire.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 SignalWire 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 SignalWire receives. The request we make on your behalf, including the key and the arguments, under SignalWire's own terms and privacy policy. SignalWire acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer SignalWire 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 SignalWire 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. SignalWire (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 SignalWire at any time to end all access.

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

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

SignalWire (BYOK) — Terms of Service

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

1. The Service. SignalWire (BYOK) provides: Read your SignalWire project setup: phone numbers, short codes, number groups, queues, video rooms and messaging registry brands with your own Project ID and API token. 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 SignalWire credentials and only access data you are allowed to access. SignalWire's terms apply to your use of SignalWire; 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 SignalWire. SignalWire 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 SignalWire returns, lightly trimmed; it may be incomplete, delayed or changed by SignalWire. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your SignalWire 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 SignalWire'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; SignalWire 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 SignalWire 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 SignalWire 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-signalwire

SignalWire (BYOK) support

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

• MCP endpoint: https://byok-signalwire.connectorbay.com/mcp
• REST API: https://byok-signalwire.connectorbay.com/openapi.json
• Live status: https://byok-signalwire.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. SignalWire (BYOK) never asks for them.