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

Twilio Task Router (BYOK) — connector documentation

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

What Twilio Task Router (BYOK) is for

Twilio Task Router (BYOK) lets an AI assistant read your own Twilio Task Router data through the Twilio Task Router 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: 11 tools (list_workspaces, get_workspace, list_workers, list_task_queues, list_workflows, list_activities, list_task_channels, list_tasks, get_workspace_realtime_statistics, get_workspace_cumulative_statistics, get_task_queue_realtime_statistics). 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 taskrouter.twilio.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Twilio Task Router. Twilio Task Router 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 TaskRouter workspaces do I have?"
  • "What are the settings of my Support TaskRouter workspace?"
  • "Which TaskRouter workers are available right now?"
  • "What task queues does my workspace have?"
  • "Which workflows route tasks in my workspace?"
  • "What worker activities are defined in my workspace?"

What it does

  • list_workspaces: List the TaskRouter workspaces of the account with their default activity and whether multi-tasking is on.
  • get_workspace: Get one TaskRouter workspace: name, default and timeout activities, event callback URL and multi-task setting.
  • list_workers: List the workers of a workspace with current activity and availability. Worker attributes are not returned.
  • list_task_queues: List the task queues of a workspace with the worker expression each one targets and its ordering.
  • list_workflows: List the workflows of a workspace with their reservation timeout and callback URLs.
  • list_activities: List the worker activities (Available, Offline and custom ones) of a workspace and whether each counts as available.
  • list_task_channels: List the task channels (voice, sms, default and custom) of a workspace.
  • list_tasks: List tasks of a workspace with status, priority, queue and workflow. Task attributes (customer data) are not returned.
  • get_workspace_realtime_statistics: Get live counts for a workspace: workers per activity, tasks by status and priority and the longest waiting task age in seconds.
  • get_workspace_cumulative_statistics: Get totals over a recent window for a workspace: tasks created, completed and canceled, reservations accepted and rejected and average acceptance time.
  • get_task_queue_realtime_statistics: Get live numbers for one task queue: tasks by status, eligible and available workers and the longest wait.

BYOK key

You bring your own Twilio Task Router 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 taskrouter.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 Task Router API (taskrouter.twilio.com) with a BYOK key; documentation: https://www.twilio.com/docs/taskrouter/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 Task Router. Twilio Task Router 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 Task Router account.

Built for: Worldwide. Languages: English.