# Recordings

#### 7.6.1 Recording List Resource URI <a href="#recording_list_resource_uri" id="recording_list_resource_uri"></a>

```php
/call/2012-04-24/Accounts/ACCOUNT_SID/Recordings
OR
/call/2012-04-24/Accounts/{AccountSid}/Recordings/{RecordingSid}
```

{% hint style="warning" %}
Unlike the Recording instance resource described above, the list of recordings IS protected by your account credentials like most parts of this API. You must use HTTP basic auth to access the Recordings list resource.\*
{% endhint %}

**HTTP GET.** Returns a list of all the Recording resources for this Account, including the properties above.\
**HTTP DELETE**  Deletes a recording that belongs to this Account.

The audio file is named using the RecordingSid and a file extension of .wav.

The URLs that contain the actual audio recordings are accessible by everyone without the need to authenticate with callapi. This is per design to allow for your apps to easily access the recordings without revealing your credentials. The same is NOT true for the resource to retrieve the list of recordings. Unauthenticated users cannot access the RecordingSid and hence not able to download the actual recording.

| Warning | Warning: Although Recording Sids in Recording URLs are essentially long random strings that are very difficult to guess, you still need to make sure that they don’t fall in the wrong hands. |
| ------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

## Resource Properties

| Property        | Description                                                                                                                 |
| --------------- | --------------------------------------------------------------------------------------------------------------------------- |
| **Sid**         | A string that uniquely identifies a recording.                                                                              |
| **DateCreated** | The date that the recording was created.                                                                                    |
| **DateUpdated** | The date that the recording was last updated.                                                                               |
| **AccountSid**  | The unique id of the Account that created the recording.                                                                    |
| **CallSid**     | The unique id of the call during which the recording was made.                                                              |
| **Duration**    | The length of the recording, in seconds.                                                                                    |
| **ApiVersion**  | The API version in use during the recording.                                                                                |
| **Uri**         | The URI for this account, relative to `https://v1.api19.com/call/2012-04-24/.`                                              |
| **FileUri**     | The File URI for this recording, relative to `https://v1.api19.com/call/2012-04-24/`. It can be used to access the WAV file |

\
Supported Operations
--------------------

&#x20;**HTTP GET.** Returns the representation of a Recording resource, including the properties above.

&#x20;**HTTP DELETE**. Removes the recording from the account.

#### Recording List Resource URI <a href="#recording_list_resource_uri" id="recording_list_resource_uri"></a>

{% hint style="info" %}
There is two types of tokens: Call API SID Token and API Token; both must be used.
{% endhint %}

###


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://apidocs.api19.com/call-apis/recordings.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.