---
title: "Get a Conference Recording"
method: GET
path: "/Accounts/{AccountSid}/Conferences/{ConferenceSid}/Recordings/{Sid}.json"
tags: ["Conference Recordings"]
---

# Get a Conference Recording

`GET /Accounts/{AccountSid}/Conferences/{ConferenceSid}/Recordings/{Sid}.json`

## Request

- Base URL: `https://YOUR_SPACE.signalwire.com/api/laml/2010-04-01`
- URL: `https://YOUR_SPACE.signalwire.com/api/laml/2010-04-01/Accounts/{AccountSid}/Conferences/{ConferenceSid}/Recordings/{Sid}.json`
- Auth: HTTP basic

Retrieves one voice-conference recording's metadata by conference SID and recording SID. Use [List Conference Recordings](/docs/compatibility-api/rest/conference-recordings/list-conference-recordings) to discover recording SIDs; Video Room recordings are separate media resources.

Request the recording URI with a `.json` extension to get the metadata. With `.mp3`, the URI responds with a `302` redirect to an MP3 version of the recording. Without an extension, the response follows the request's `Accept` header: `application/json` returns the metadata, and a generic value such as `*/*` redirects to a WAV version. When the recording has no audio to return, for example because its `status` isn't `completed`, the audio URIs respond with `404` and an empty body.

Access follows the project's **Protect Recording Media URLs** setting, which new projects have turned on. When it's on, authenticate with your Project ID and an API token that has the _Management_ scope; otherwise the request gets a `401`. When it's off, anyone with the URI can retrieve the recording without authenticating. See [Retrieve a Recording](/docs/compatibility-api/rest/recordings/retrieve-recording) for details.

## Path parameters

- `AccountSid` string, uuid, required: Universal Unique Identifier.
- `ConferenceSid` string, uuid, required: Universal Unique Identifier.
- `Sid` string, uuid, required: Universal Unique Identifier.

## Response `200`

The request has succeeded.

- ConferenceRecordingResponse: Response containing a single conference recording.
  - `sid` string, uuid, required: Universal Unique Identifier.
  - `account_sid` string, uuid, required: Universal Unique Identifier.
  - `api_version` string, required: The version of the SignalWire API.
  - `call_sid` string, nullable, required: The unique identifier for the call. Always null for conference recordings.
  - `conference_sid` string, uuid, required: Universal Unique Identifier.
  - `channel` '1' | '2', required: The number of channels in a recording (singular key). Returns '1' for mono or '2' for stereo.
  - `channels` '1' | '2', required: The number of channels in a recording. Returns '1' for mono or '2' for stereo.
  - `date_created` string, required: The date, in RFC 2822 format, this recording was created.
  - `date_updated` string, required: The date, in RFC 2822 format, this recording was updated.
  - `start_time` string, nullable, required: The time, in RFC 2822 format, this recording started.
  - `end_time` string, nullable, required: The time, in RFC 2822 format, this recording ended.
  - `duration` integer, required: The length, in seconds, of the recording.
  - `price` number, double, required: The cost of the recording.
  - `price_unit` string, required: The currency of the price of the recording.
  - `source` 'Conference', required: Recording source for conference recordings. Always `Conference`.
  - `status` 'queued' | 'in-progress' | 'paused' | 'resumed' | 'completed' | 'absent' | 'stopped', required: Recording status.
  - `error_code` string, nullable, required: Further details about a failed recording.
  - `uri` string, required: The URI of the recording.
  - `subresource_uris` ConferenceRecordingSubresourceUris, required: Recording subresource URIs.
    - `transcriptions` string, required: The URI for transcriptions.
  - `encryption_details` string, nullable, required: Encryption details. Always null.
  - `trim` string, nullable, required: Whether leading and trailing silence is trimmed from a recording: `trim-silence` or `do-not-trim`. Can be null, for example on conference recordings.

## Other responses

- `400`: The request was invalid or cannot be processed. Check the error details for more information.
- `401`: Authentication failed. Please verify your credentials and try again. The body is usually the plain text `Unauthorized`. If your Space hasn't verified a phone number yet, the body is JSON instead: `{"message": "Please validate a phone number to access your account."}`.
- `404`: The requested resource was not found. Please verify the resource identifier.

## Changes

- **2026-10-29** `d09479744b3d`: 1 breaking, 1 info
  - removed the media type `application/json` for the response with the status `401`
  - added the media type `text/plain` for the response with the status `401`
- **2026-10-29** `29659db8352c`: 1 info
  - removed the `StartConferenceRecording` enum value from the `source/allOf[#/components/schemas/ConferenceRecordingSource]/` response property for the response status `200`
- **2026-10-29** `d2ecf7cc758f`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/signalwire/apis/compatibility-api/changes/Accounts/:AccountSid/Conferences/:ConferenceSid/Recordings/:Sid.json/get.md)

---

[API](https://skmtc.dev/signalwire/apis/compatibility-api.md) - [All operations](https://skmtc.dev/signalwire/apis/compatibility-api/llms.txt) - [OpenAPI document](https://skmtc.dev/signalwire/apis/compatibility-api/revisions/d09479744b3d?raw)