---
title: "Send DTMF to conference participants"
method: POST
path: "/conferences/{id}/actions/send_dtmf"
tags: ["Conference Commands"]
---

# Send DTMF to conference participants

`POST /conferences/{id}/actions/send_dtmf`

Send DTMF tones to one or more conference participants.

## Path parameters

- `id` string, uuid, required

## Request body

- ConferenceSendDTMFRequest
  - `digits` string, required — DTMF digits to send. Valid characters: 0-9, A-D, *, #, w (0.5s pause), W (1s pause).
  - `call_control_ids` string[] — Array of participant call control IDs to send DTMF to. When empty, DTMF will be sent to all participants.
  - `duration_millis` integer — Duration of each DTMF digit in milliseconds.
  - `client_state` string — Use this field to add state to every subsequent webhook. Must be a valid Base-64 encoded string.

## Response `200`

Successful response upon making a conference command.

- object
  - `data` ConferenceCommandResult
    - `result` string, required

## Other responses

- `401` — Unauthorized. Authentication failed - the required authentication headers were either invalid or not included in the request.
- `404` — Resource not found. The requested resource does not exist. Common causes include: invalid call_control_id, conference not found, audio file not found, or recording not found.
- `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.

---

[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)