---
title: "Remove Participant"
method: DELETE
path: "/conferences/{id}/participants/{participant}"
tags: ["Conferences > participants"]
---

# Remove Participant

`DELETE /conferences/{id}/participants/{participant}`

## Request

- Base URL: `https://api.pinnacle.sh`
- URL: `https://api.pinnacle.sh/conferences/{id}/participants/{participant}`
- Auth: API key in header `PINNACLE-API-KEY`

Hang up this participant's call. Everyone else stays in the conference.

## Path parameters

- `id` string, required
- `participant` string, required

## Response `200`

The removed participant (`left_reason` is `removed`).

- Participant: A call in a conference.
  - `call_id` string, required: The participant is this call; every call API works on it.
  - `conference_id` string, required
  - `label` string, nullable, required
  - `status` 'dialing' | 'ringing' | 'joined' | 'left' | 'failed', required: - `dialing`: A dialed participant whose call hasn't answered yet. - `ringing`: Answered and being connected (or hearing its `announce`). - `joined`: In the conference. - `left`: Hung up or was removed. - `failed`: Never connected (busy, no answer, rejected, or an error).
  - `from` string, nullable, required
  - `to` string, nullable, required
  - `muted` boolean, required: Nobody hears this participant; they still hear everyone.
  - `on_hold` boolean, required: They hear hold audio and nobody hears them.
  - `whisper_to` string[], nullable, required: Call IDs of the only participants who can hear this one, or `null` for everyone.
  - `end_conference_on_leave` boolean, required: When this participant leaves, the conference ends for everyone.
  - `joined_at` string, date-time, nullable, required
  - `left_at` string, date-time, nullable, required
  - `left_reason` 'hangup' | 'removed' | 'busy' | 'no_answer' | 'rejected' | 'failed' | 'conference_ended', required

## Other responses

- `401`: The request lacks valid authentication credentials or the provided credentials are invalid. <br> Ensure you're including a valid API key in the request headers and that your account has the necessary permissions to access this endpoint.
- `404`: The requested resource could not be found. <br> This may occur if the identifier is incorrect, the resource has been deleted, or you don't have permission to access it.
- `500`: An unexpected error occurred on Pinnacle's servers while processing your request. <br> If this error persists, please contact support with the request details.
- `502`: One of Pinnacle's providers failed. Please try again later.

---

[API](https://skmtc.dev/pinnacle/apis/pinnacle-2.md) - [All operations](https://skmtc.dev/pinnacle/apis/pinnacle-2/llms.txt) - [OpenAPI document](https://skmtc.dev/pinnacle/apis/pinnacle-2/revisions/45416dadab79?raw)