> For the complete documentation index, see [llms.txt](https://docs.enapi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enapi.com/cdr-clearing/exporting-cdr-data.md).

# Exporting CDR Data

Get cleared CDRs out of ENAPI and into your invoicing workflow.

### Exporting from the inbox

{% stepper %}
{% step %}
Navigate to **CDRs → Inbox**
{% endstep %}

{% step %}
**Apply filters:** Typically the billing period and partner.
{% endstep %}

{% step %}
Click **Export**
{% endstep %}

{% step %}
Confirm the number of records: Check the number of records in the modal and click **Export**.
{% endstep %}

{% step %}
**Download the CSV:** You'll receive an email with a link to download the CSV, active for 24 hours.
{% endstep %}
{% endstepper %}

The export covers whatever's currently visible. Exporting from **To Review** gives you only CDRs pending review; exporting from **All CDRs** with no filters gives you everything. Large exports may take a few minutes to process.

<figure><img src="https://303450155-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FheBP0sH0U1Rrp1jIot9S%2Fuploads%2FZXA4G1FJZP7RvLbYo9kK%2Fimage%20(58).png?alt=media&amp;token=903bbf1d-bdc3-4d35-8335-e53f69ee0a7b" alt="" width="563"><figcaption><p>Export CDRs to CSV.</p></figcaption></figure>

### What's in the export

Every visible column plus:

* Full timestamps (created, start, end).
* Party information (country codes, party IDs).
* Session data (ID, linked metadata).
* Financial data (cost, calculated cost, currency).
* Location data (location ID, EVSE, connector).
* Token data (token used, authorization method).
* Status information (your status, partner status, inbox state).

### Export tips

* Filter by **session start date** rather than creation date for billing-period exports — sessions that ran in March but whose CDRs arrived in April should count toward March.
* Filter by **partner party ID** for per-partner exports.
* Use the **Passed/Failed** filter to cleanly separate billable data from still-under-investigation data.


---

# 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://docs.enapi.com/cdr-clearing/exporting-cdr-data.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.