> For the complete documentation index, see [llms.txt](https://answeringservicecare.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://answeringservicecare.com/docs/api-reference/user-portal-apis/call-recordings.md).

# Call Recordings

The **Call Recordings** API exposes the audio and metadata for calls handled by Answering Service Care, inbound, outbound, and AI-assisted. Recordings are retrievable by ID, or in bulk with filters that match how call data is usually reviewed in practice.

> **Retention (per privacy policy):**
>
> * **Call recordings (audio)**, retained for up to **31 days**. After that, the `recording` URL will no longer resolve.
> * **Call detail records (CDR metadata)**, retained for up to **3 years**. The `cdr` object on each recording persists beyond the 31-day audio window.

#### What you can do

* **List** recordings with filters for `account_id`, `skill_name`, date range (`from_date` / `to_date` in `MM-DD-YYYY`), and a `sample` flag that returns a representative subset rather than every call in the window (handy for QA sampling without pulling thousands of files).
* **Retrieve** a single recording by ID with its full metadata payload, including a nested CDR (call detail record) with agent, skill, and timing information.

#### Common use cases

* Pulling a weekly QA sample into a call-review tool.
* Fetching all recordings for a specific account during a dispute investigation.
* Syncing recordings into long-term archival storage (within the 31-day window), filtered by skill.

Recording objects include participant metadata, skill routing, the call's associated account, a time-limited URL to the audio file, and the full CDR.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://answeringservicecare.com/docs/api-reference/user-portal-apis/call-recordings.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.