> ## Documentation Index
> Fetch the complete documentation index at: https://developers.telnyx.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Recording

> What the meeting recording is, and where to fetch it once the meeting ends.

A meeting session records automatically. Point the bot at a meeting and the recording is produced alongside the transcript -- there is nothing to switch on.

That is why `POST /v2/meeting_sessions` has no recording parameter and no action controls it: the session's three actions are [`speak`, `stop_speaking`](/docs/meeting/control/speak) and [`send_chat`](/docs/meeting/control/chat). Recording is not something you start, stop, or configure, so the only calls you make are the ones that read the result afterwards.

What that leaves you:

* The `recording.available` webhook fires when a recording is ready. It carries only `recording_types` and never URLs.
* `GET /v2/meeting_sessions/{id}/recordings` returns the available recordings with short-lived signed download URLs. Re-fetch it whenever you need a current URL rather than storing one.
* `DELETE /v2/meeting_sessions/{id}/recording_media` removes the media. The session, its transcript, events and artifacts are kept.
* A [digital avatar's](/docs/meeting/digital-avatars) camera video is not included in the provider recording; the bot's audio is.

Fetching and deleting recordings is covered with the rest of the post-meeting data in [Collect Results](/docs/meeting/collect-results#recordings).

## Related

* [Collect Results](/docs/meeting/collect-results) -- fetch recordings, the finalized transcript, and artifacts
* [Webhooks](/docs/meeting/webhooks) -- receive `recording.available`
* [Session Events](/docs/meeting/events) -- the ordered event history for a session