Retrieve a Recording.
Retrieve a single recording media or its metadata.
Access to recording files with a direct URL is useful because they are public and do not require Basic Auth. This allows external applications to embed recording URLs without exposing their SignalWire API credentials. SignalWire recording URLs are long and random, making them difficult to guess or exploit unless you reveal the URL.
Retrieve WAV file
When a recording URI has no extension or a .wav
extension, the request
will return a binary WAV version of the recording file.
GET https://example.signalwire.com/api/laml/2010-04-01/Accounts/{AccountSid}/Recordings/{Sid}
GET https://example.signalwire.com/api/laml/2010-04-01/Accounts/{AccountSid}/Recordings/{Sid}.wav
Retrieve MP3 file
Setting an extension of ".mp3" on the URI returns a binary MP3 version of the recording. For example:
GET https://example.signalwire.com/api/laml/2010-04-01/Accounts/{AccountSid}/Recordings/{Sid}.mp3
Retrieve Metadata
A recording's metadata, such as duration, cost, time, can be returned by
setting the Recording URI's extension to .json
. For example:
GET https://example.signalwire.com/api/laml/2010-04-01/Accounts/{AccountSid}/Recordings/{Sid}.json
Permissions
The API token must include the following scopes: Voice.
Path Parameters |
---|
AccountSid uuid — REQUIREDThe unique identifier for the account that is associated with this recording. |
Sid uuid — REQUIREDThe unique identifier for the recording. |
Responses | |||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
200 OK
|