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

Twilio Queues and Conferences (BYOK) — connector documentation

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

What Twilio Queues and Conferences (BYOK) is for

Twilio Queues and Conferences (BYOK) lets an AI assistant read your own Twilio Queues and Conferences data through the Twilio Queues and Conferences 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: 8 tools (list_queues, get_queue, list_queue_members, list_conferences, get_conference, list_conference_participants, list_applications, list_recordings). 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.twilio.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Twilio Queues and Conferences. Twilio Queues and Conferences 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:

  • "How many callers are waiting in my Twilio queues?"
  • "How long is the wait in queue QU...?"
  • "Who is waiting in queue QU... and for how long?"
  • "Which Twilio conferences are in progress?"
  • "Why did conference CF... end?"
  • "Who is muted in conference CF...?"

What it does

  • list_queues: List call queues with current size, maximum size and average wait time in seconds.
  • get_queue: Get one queue: current size, maximum size and average wait time.
  • list_queue_members: List the calls waiting in one queue with position and wait time in seconds. Caller numbers are not returned.
  • list_conferences: List conferences with name, status (init, in-progress, completed), region and why they ended.
  • get_conference: Get one conference: name, status, region, end reason and dates.
  • list_conference_participants: List the participants of one conference with call SID, label, muted, hold and coaching flags and status. Phone numbers are not returned.
  • list_applications: List TwiML applications with voice and SMS webhook URLs.
  • list_recordings: List recording metadata (call, conference, duration, status, source, price). The audio and media URL are not returned.

BYOK key

You bring your own Twilio Queues and Conferences 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 api.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 Queues and Conferences API (api.twilio.com) with a BYOK key; documentation: https://www.twilio.com/docs/voice/api/conference-resource. 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 Queues and Conferences. Twilio Queues and Conferences 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 Queues and Conferences account.

Built for: Worldwide. Languages: English.