---
title: "Enqueue call"
method: POST
path: "/calls/{call_control_id}/actions/enqueue"
tags: ["Call Commands"]
---

# Enqueue call

`POST /calls/{call_control_id}/actions/enqueue`

Put the call in a queue.

## Path parameters

- `call_control_id` string, required

## Request body

- EnqueueRequest
  - `queue_name` string, required — The name of the queue the call should be put in. If a queue with a given name doesn't exist yet it will be created.
  - `client_state` string — Use this field to add state to every subsequent webhook. It must be a valid Base-64 encoded string.
  - `command_id` string — Use this field to avoid duplicate commands. Telnyx will ignore any command with the same `command_id` for the same `call_control_id`.
  - `max_wait_time_secs` integer — The number of seconds after which the call will be removed from the queue.
  - `max_size` integer — The maximum number of calls allowed in the queue at a given time. Can't be modified for an existing queue.
  - `keep_after_hangup` boolean — If set to true, the call will remain in the queue after hangup. In this case bridging to such call will fail with necessary information needed to re-establish the call.

## Response `200`

Successful response upon making a call control command.

- object
  - `data` CallControlCommandResult
    - `result` string

## Other responses

- `422` — Unprocessable entity. The request was well-formed but could not be processed due to semantic errors. This includes validation errors, invalid parameter values, call state errors, conference errors, queue errors, recording/transcription errors, and business logic violations.
- `default` — Unexpected error

---

[API](https://skmtc.net/team-telnyx/apis/telnyx-api-2.md) · [All operations](https://skmtc.net/team-telnyx/apis/telnyx-api-2/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/team-telnyx/telnyx-api-2/versions/8f5f4e537994/schema)