Pagination
This endpoint follows the standard list contract: data is the array of the current queue's numbers (ordered by position ascending), alongside a top-level pagination block.
page— 1-indexed page number (default1).size— numbers per page (default20, max100).- Read
pagination(total_count,total_pages,has_more) to page through the full list.
The queue's own metadata (id, name, voicemail_handling, do_not_disturb, creator/assignee) is returned under the top-level queue key — without the numbers, since those are paginated in data. The queue field stays the same across pages.
When the user has no queue, the response is 200 with an empty data array, a zeroed pagination, and no queue key — not a 404.
Reading call_status
Each number in data carries a call_status field: one status per row, derived from the call placed for it. Use it instead of combining routing_result, not_reached_destination_reason and detected_outbound_voicemail yourself.
| Value | Meaning |
|---|---|
QUEUED | No call has been placed yet, or the call is still in progress. |
SKIPPED | The number was skipped in the Power Dialer and no call was placed. If a call is placed for it later, the status follows that call. |
VOICEMAIL | The call reached a voicemail box. |
CONNECTED | The call was answered at route level (routing_result is ANSWERED) no voicemail was detected and no not_reached_destination_reason is set. |
TRANSFERRED | The call was transferred. |
BUSY | The destination was busy. |
WRONG_NUMBER | The destination is not in service. |
NO_ANSWER | The call ended without an answer: declined, unavailable, ring timeout, network error, or any other final route status (failed, blocked, closed, handled by call flow). |
CONNECTED means the call was answered at route level, not that a conversation took place, so it can over-report real conversations.
A number whose call is in progress shows QUEUED. Counting QUEUED numbers can therefore differ from the remaining count while a call is running.
Targeting a teammate's queue
By default, this returns the queue assigned to the API key owner. To inspect a teammate's queue, pass either user_id or email as a query parameter. The teammate must belong to the same team as the API key owner.
user_id— wins when both are provided. Resolve teammate ids viaGET /v2/api/users.email— used only whenuser_idis absent.
If the resolved user isn't on your team, the response is 404 ASSIGNEE_NOT_FOUND — the same error is returned whether the user doesn't exist or isn't a teammate, so API consumers cannot enumerate users.