Skip to main content
POST
/
v2
/
api
/
dialing-queues
/
current
curl --request POST \
  --url https://api.withallo.com/v2/api/dialing-queues/current \
  --header 'Authorization: <api-key>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "name": "Monday cold calls"
}
'
{
  "data": {
    "id": "pdl_2xGh7kLmNpQr",
    "name": "Monday cold calls",
    "creator_id": "usr_abc123",
    "assignee_id": "usr_abc123",
    "voicemail_handling": "NO_SKIP",
    "do_not_disturb": "DISABLED",
    "numbers": [],
    "created_at": "2026-05-06T10:00:00",
    "updated_at": "2026-05-06T10:00:00"
  }
}

Targeting a teammate’s queue

By default, this creates an empty queue for the API key owner. To create the queue for a teammate instead, send user_id or email in the JSON body. 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.
The API key owner is recorded as creator_id and the teammate as assignee_id. If the resolved user isn’t on your team, the response is 404 ASSIGNEE_NOT_FOUND.

Authorizations

Authorization
string
header
required

Body

application/json

Optional payload for resetting a queue. Send an empty body to reset your own queue without renaming.

name
string | null

Display name for the new queue (max 255 characters). Leave unset to create the queue without a name.

Maximum string length: 255
user_id
string | null

Optional. ID of a teammate the new queue should be assigned to. The API key owner is recorded as creator_id. The teammate must belong to the same team as the API key owner. Wins over email when both are provided.

Example:

"usr-15BB68317A7F06F0C07A3BBD8F244102A6872220"

email
string<email> | null

Optional. Email of a teammate the new queue should be assigned to. Ignored when user_id is also supplied.

Response

The newly created (empty) queue

data
object

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