The WhatsApp numbers this workspace can send from
Every WhatsApp Business number configured on the workspace, with the agent that owns it, its WABA, and the queues it is routed to.
When to use it. Before starting a new outbound WhatsApp conversation, so the operator picks which number the customer sees. agent_uuid from the chosen entry is exactly what POST /whatsapp/template wants as agentId, and passing the same value to GET /whatsapp/templates?agent_uuid=… narrows the catalogue to the templates that number’s WABA has actually approved. Picking the number first and the template second is what stops a send failing at Meta.
Why the list exists. The same information can be assembled by paging GET /agents and filtering channels[], but that reads every agent record on the workspace to find a handful of numbers. This answers it directly.
sendable. True when the number can actually originate a message: it is active and reachable through an agent (agent_uuid present) with a Meta phone number id. A number that is configured for receiving but has no agent behind it comes back sendable: false with agent_uuid: null — show it disabled rather than hiding it, so the gap is visible to whoever administers the workspace.
queues. The queues this number is routed to, from the queue designer. Note that a queue’s channel also names an ai_agent — that is who answers on the number, which is not necessarily the agent that sends from it.
Who can call it, and how much of it they see. A workspace API token, or a per-user JWT holding loop.templates.send. A workspace token — and an admin or the workspace owner on a JWT — gets every number. Any other per-user JWT gets only the numbers routed to an ACTIVE queue that user is a member of, the same membership rule the inbox reads by; a number routed to no queue is workspace/admin-only.
Authorizations
Use a Bearer token to access these API endpoints. Example: "Bearer {your-token}"
Query Parameters
Return only numbers that can originate a message
Only numbers routed to this queue