Skip to main content
GET
/
v2
/
api
/
dialing-queues
/
current
Get current queue
curl --request GET \
  --url https://api.withallo.com/v2/api/dialing-queues/current \
  --header 'Authorization: <api-key>'
{
  "data": {
    "id": "pdl_2xGh7kLmNpQr",
    "name": "My Queue",
    "creator_id": "usr_abc123",
    "assignee_id": "usr_abc123",
    "numbers": [
      {
        "number_to": "+12125550010",
        "position": 0,
        "created_at": "2026-04-30T10:00:00",
        "updated_at": "2026-04-30T10:00:00"
      }
    ],
    "created_at": "2026-04-30T10:00:00",
    "updated_at": "2026-04-30T10:00:00"
  }
}

​
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 via GET /v2/api/users.
  • email — used only when user_id is 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.

Authorizations

​
Authorization
string
header
required

Query Parameters

​
user_id
string

ID of a teammate to read the queue for. Resolve teammate ids via GET /v2/api/users. Wins over email when both are provided.

Example:

"usr-15BB68317A7F06F0C07A3BBD8F244102A6872220"

​
email
string<email>

Email of a teammate to read the queue for. Ignored when user_id is also supplied.

Example:

"[email protected]"

Response

The targeted user's Power Dialer queue

​
data
object

A user's Power Dialer queue with its configuration and numbers.