Get a Conference Recording
Retrieves one voice-conference recording’s metadata by conference SID and recording SID. Use 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 for details.
Authentication
SignalWire Basic Authentication using Project ID and API Token.
The client sends HTTP requests with the Authorization header containing the word Basic followed by a space and a base64-encoded string of project_id:token. The project ID will be used as the username and the API token as the password.
Example:
Authorization: Basic base64(project_id:token)
Path parameters
Response
The number of channels in a recording (singular key). Returns ‘1’ for mono or ‘2’ for stereo.
Whether leading and trailing silence is trimmed from a recording: trim-silence or do-not-trim. Can be null, for example on conference recordings.