---
title: "Toggle recording on a live call channel"
method: POST
path: "/channels/{channelId}/events/record/toggle"
tags: ["channels"]
---

# Toggle recording on a live call channel

`POST /channels/{channelId}/events/record/toggle`

Toggles call recording on a live call channel. If the call is not being recorded, recording starts — the audio is captured and stored for later retrieval via `GET /calls/{callId}/channels/{channelId}`. If already recording, it stops. This is a real-time telephony control — the effect is immediate.

The `channelId` identifies a specific participant's leg in the call. Use `POST /calls/current` to discover active channel IDs. Recording availability also depends on the team's recording policy configuration.

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

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

## Path parameters

- `channelId` string, required

## Response `201`

Successfully processed — the recording toggle event has been applied to the channel.

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