> ## Documentation Index
> Fetch the complete documentation index at: https://docs.command.cleargrid.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Data Exports Overview

> Read your operational data out of Command via paginated exports

The Exports API gives you paginated, read-only access to the ClearGrid datasets that belong to your lender. Every row returned is scoped to the calling lender and passed through an allowlist that strips and masks sensitive fields, so you can pull operational data into your own warehouse without handling raw PII.

There are two endpoints. The [catalog endpoint](/api-reference/exports/endpoints/catalog) lists what is available to you, and the [fetch-dataset endpoint](/api-reference/exports/endpoints/fetch-dataset) retrieves the rows. Both endpoints use the same cursor-based pagination, which supports an initial full bootstrap and ongoing incremental delta loads from one consistent interface.

<Note>
  The catalog lists **25 dataset codes** across five sections. As of **v1.2, 19 codes are available** to fetch today. The remaining **6 codes** (D04, D06, D10, D11, D13, D24) are reserved for future use and listed with `available: false`. Fetching any dataset with `available: false` returns a `404`.
</Note>

## Endpoints

<CardGroup cols={2}>
  <Card title="Catalog endpoint" icon="list" href="/api-reference/exports/endpoints/catalog">
    Discover the sections and datasets you are allowed to export, with cursor fields and availability flags.
  </Card>

  <Card title="Fetch dataset endpoint" icon="download" href="/api-reference/exports/endpoints/fetch-dataset">
    Retrieve paginated, redacted rows for a single dataset, for both initial and incremental loads.
  </Card>
</CardGroup>

## Available datasets at a glance

| Code | Dataset                            | Cursor field      | Typical use                              |
| ---- | ---------------------------------- | ----------------- | ---------------------------------------- |
| D01  | Borrowers                          | `updated_at`      | Customer master                          |
| D02  | Borrower Accounts                  | `updated_at`      | Account / loan portfolio                 |
| D03  | Borrower Sub Accounts              | `updated_at`      | Per-instalment balance trail             |
| D05  | Borrower Account Events            | `created_at`      | Channel / status events                  |
| D07  | Borrower Payments                  | `updated_at`      | Payment events                           |
| D08  | Borrower Payment Plans             | `updated_at`      | Payment plan headers                     |
| D09  | Borrower Payment Plan Installments | `updated_at`      | Per-installment rows                     |
| D12  | Scheduled Payments                 | `updated_at`      | Future-dated payment instructions        |
| D14  | Payment Proofs                     | `updated_at`      | Uploaded receipts metadata               |
| D15  | Borrower Settlements               | `updated_at`      | Settlement / promise-to-pay plans        |
| D16  | Borrower Deals                     | `updated_at`      | Collections case state                   |
| D17  | Borrower Deal Activity Logs        | `created_at`      | Per-case activity                        |
| D18  | Borrower Deal Logs                 | `created_at`      | Case state snapshots                     |
| D19  | Deal Activity Logs                 | `created_at`      | Deal-level activity                      |
| D20  | Deal Views                         | `updated_at`      | Saved deal filters                       |
| D21  | Communication Logs                 | `communicated_at` | Per-attempt operational call & email log |
| D22  | Conversations                      | `updated_at`      | Email and messaging threads              |
| D23  | Manual Communication Logs          | `communicated_at` | Agent's outreach outcomes                |
| D26  | User Lender Details                | `updated_at`      | Borrower-×-lender link                   |

## Date and time formats

Exports return **two distinct date conventions**, depending on how the field is stored at source — parse them with separate handling:

* **System timestamps** — `created_at`, `updated_at`, `communicated_at`, and any genuine `Date`-typed field (e.g. the PTP / broken-PTP dates on `D16`) are **ISO-8601** with milliseconds and a `Z` suffix (e.g. `2026-05-28T11:42:08.000Z`).
* **Business date columns** — certain date fields are stored as plain strings and are returned **exactly as stored, in `DD/MM/YYYY`** (e.g. `22/02/2026`). They are **not** normalized to ISO-8601, carry no time component, and no timezone. Confirmed `DD/MM/YYYY` fields today: `D02` / `D03` `submitted_date` and `due_date`, and `D16` `dpd_due_date` and `last_due_date`.

<Warning>
  If you ingest into a typed warehouse (e.g. BigQuery), do **not** map the business date columns to a `TIMESTAMP`/`DATE` type expecting ISO-8601 — ingest them as `STRING` and parse `DD/MM/YYYY`, or transform on the way in. Mapping them as native dates will fail or silently misparse (e.g. day/month inversion).
</Warning>

## Quick reference

<CardGroup cols={3}>
  <Card title="Pagination" icon="arrow-right" href="/api-reference/exports/pagination">
    Cursor encoding, initial vs. incremental loads, and variable page-size behavior.
  </Card>

  <Card title="Errors" icon="triangle-exclamation" href="/api-reference/exports/errors">
    Every status code the export endpoints return, with example bodies.
  </Card>

  <Card title="Datasets" icon="table" href="/api-reference/exports/datasets/d07-borrower-payments">
    Field-by-field reference for each Phase 1 dataset.
  </Card>
</CardGroup>

***

<Snippet file="snippets/support-info.mdx" />