WIwithallo
Power Dialer

Append numbers to queue

Changed on

Appends phone numbers to the Power Dialer queue assigned to the authenticated user. Creates the queue implicitly if none exists. Send user_id or email to append to a teammate's queue — if that teammate has no current queue, one is created with the API key owner as creator_id and the teammate as assignee_id. user_id wins when both are provided.

post/v2/api/dialing-queues/current/numbers

Request

  • Base URL
    https://api.withallo.com
  • URL
    https://api.withallo.com/v2/api/dialing-queues/current/numbers
  • Auth
    API key in header Authorization

Request body

user_idstring nullable

Optional. ID of a teammate whose queue should receive the numbers. The teammate must belong to the same team as the API key owner. Wins over email when both are provided. Resolve teammate ids via GET /v2/api/users.

emailstring email nullable

Optional. Email of a teammate whose queue should receive the numbers. Ignored when user_id is also supplied.

date_order'DAY_FIRST' | 'MONTH_FIRST' nullable

Optional. How to read numeric DATE values in custom_attributes such as 03/04/2026: DAY_FIRST (3 April) or MONTH_FIRST (4 March). Applies to every date field in the request. When absent, each date field is read in the order its values settle (a 13/04/2026 can only be day first); when none settle it, your phone number's country decides: month first for the US, day first everywhere else.

Example request

{
  "numbers": [
    {
      "custom_attributes": {
        "lead_source": "Webinar",
        "deal_size": "1200",
        "next_meeting": "2026-11-03"
      }
    }
  ],
  "user_id": "usr-15BB68317A7F06F0C07A3BBD8F244102A6872220",
  "email": "teammate@acme.com",
  "date_order": "DAY_FIRST"
}

Response

Numbers appended

Example response

{
  "data": {
    "ignored_custom_attributes": [
      {
        "number": "+12125550010",
        "keys": [
          "unknown_field"
        ]
      }
    ]
  }
}

Changes

  • 46c77103dd14Revision changes
    • breaking

      the response's body type changed from no type to object for status

    • breaking

      the response's body type changed from no type to object for status

    • breaking

      the response's body type changed from no type to object for status

    • warning

      added the new INVALID_CUSTOM_ATTRIBUTE_VALUE enum value to the /// response property for the response status

    • warning

      added the new UNKNOWN_CUSTOM_ATTRIBUTE enum value to the /// response property for the response status

    • info

      added the new optional request property

    • info

      added the new optional request property //

    • info

      added the optional property /// to the response with the status

    • info

      added the optional property / to the response with the status

    • info

      added the optional property to the response with the status

    • info

      added the optional property to the response with the status

    • info

      added the optional property to the response with the status