---
title: "Hang up a live call channel"
method: POST
path: "/channels/{channelId}/events/hangup"
tags: ["channels"]
---

# Hang up a live call channel

`POST /channels/{channelId}/events/hangup`

Terminates (hangs up) a live call on the specified channel. The call is immediately disconnected for the participant identified by this channel. If the call has only two participants, the entire call ends. If the call involves multiple participants (e.g., conference or transfer), only the specified participant is disconnected.

The `channelId` identifies a specific participant's leg in the call. Use `POST /calls/current` to discover active channel IDs.

**Permission:** `Calls Write` required.

**Monitoring:** **Required.** This is a live call supervisory control. Returns `401 Unauthorized` if Monitoring is OFF on your API key.

> **Warning:** This action is immediate and irreversible — the call cannot be resumed after hangup.

## Path parameters

- `channelId` string, required

## Response `201`

Successfully processed — the call on the channel has been hung up.

## Other responses

- `400` — Invalid channel ID format.
- `401` — Unauthorized — missing or invalid token, or Monitoring is not enabled on your API key.
- `404` — Channel not found — no active call channel matches the provided ID.
- `500` — Internal server error.
- `502` — Service temporarily unavailable — please retry later.

---

[API](https://skmtc.net/ringover/apis/ringover-public-api.md) · [All operations](https://skmtc.net/ringover/apis/ringover-public-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/ringover/ringover-public-api/revisions/9da73dd2f99e/schema)