> ## Documentation Index
> Fetch the complete documentation index at: https://developers.pleo.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> Overview of the Export API v0, v1 and v2 deprecation. Use it to pick the guide that matches the version in your paths (/v0/, /v1/ or /v2/). All three lead to Export API (v3). The export workflow does not change.

Export API v0, v1 and v2 are replaced by Export API (v3). The workflow does not change. You still create or detect an Export Job, fetch its Export Items and update the status of each item. The version number in the endpoint changes, and v3 returns more data. Choose a migration path based on the version you use today.

> **Use this page to answer:**

### Which Export API migration guide do I use?

Look at the path that your integration calls.

* If it starts with `/v2/`, use [Migrate from Export API v2 to v3](https://developers.pleo.io/deprecation/legacy-export-api/migrate-from-v2-to-v3.md).
* If it starts with `/v1/`, use [Migrate from Export API v1 to v3](https://developers.pleo.io/deprecation/legacy-export-api/migrate-from-v1-to-v3.md).
* If it starts with `/v0/`, use [Migrate from Export API v0 to v3](https://developers.pleo.io/deprecation/legacy-export-api/migrate-from-v0-to-v3.md).

Each guide goes directly to Export API (v3). Do not migrate through an intermediate version. The export workflow does not change.

### What changes in every version of the migration?

Make these changes in every guide:

* Change the version in the path to `/v3/`.
* Replace the `status` query parameter of `GET /v3/export-jobs` with `statuses`.
* Replace `teamCode` with `team.code`.
* Ignore fields that you do not know, and accept values that you do not know for fields such as `type`, `status` and `failureReasonType`.
* Map contra accounts before you create an Export Job.

> This page is the starting point for the legacy Export API deprecation. It does not hold the migration steps. Go to the guide for your version:
>
> * [Migrate from v0 to v3](https://developers.pleo.io/deprecation/legacy-export-api/migrate-from-v0-to-v3.md)
> * [Migrate from v1 to v3](https://developers.pleo.io/deprecation/legacy-export-api/migrate-from-v1-to-v3.md)
> * [Migrate from v2 to v3](https://developers.pleo.io/deprecation/legacy-export-api/migrate-from-v2-to-v3.md)

> **Sources for the Export API:**
>
> * OpenAPI reference: the endpoint pages under the [Export API Overview](https://developers.pleo.io/reference/export-api/export-api-overview.md). Use the v3 pages for new work. The [Export API Workflow](https://developers.pleo.io/reference/export-api/export-api-workflow.md) explains the order of the calls.
> * Attachments: [Attachments](https://developers.pleo.io/docs/current/platform/exports/attachments.md) explains the receipt file limits.
> * How-tos, all under `/docs/current/how-tos/accounting-integrations/`: [How to Detect and Start Export Jobs for Processing](https://developers.pleo.io/docs/current/how-tos/accounting-integrations/how-to-detect-and-start-export-jobs-for-as-erp-processing.md), [How to Retrieve Export Job Items for Processing](https://developers.pleo.io/docs/current/how-tos/accounting-integrations/how-to-retrieve-export-job-items-for-as-erp-processing.md), [How to Fetch Export Item Data for Processing](https://developers.pleo.io/docs/current/how-tos/accounting-integrations/how-to-fetch-export-item-data-for-as-erp-processing.md), [How to Transfer Attachments](https://developers.pleo.io/docs/current/how-tos/accounting-integrations/how-to-transfer-attachments-for-as-erp-processing.md), [How to Update Export Items](https://developers.pleo.io/docs/current/how-tos/accounting-integrations/how-to-update-export-items-for-as-erp-processing.md) and [How to Update & Complete the Export Job](https://developers.pleo.io/docs/current/how-tos/accounting-integrations/how-to-update-and-complete-export-job-for-as-erp-processing.md).
> * If a how-to and the reference disagree, trust the how-to. How-tos record tested behaviour.

Terminology: Legacy and New

These guides call Export API v0, v1 and v2 the **legacy Export API**. They call the replacement the **new Export API (v3)**.

All versions are under `https://external.pleo.io`. The version is the first part of the path, for example `/v2/export-jobs` or `/v3/export-jobs`.

## Which guide do you need?

Look at the paths that your integration calls. If they start with `/v2/`, use the v2 guide. If they start with `/v1/`, use the v1 guide. If they start with `/v0/`, use the v0 guide.

> [card] [Migrate from Export API v2 to v3](https://developers.pleo.io/deprecation/legacy-export-api/migrate-from-v2-to-v3.md)
>
> For integrations on `/v2/`. Change the version in the path. The payload has the same structure and v3 adds fields.

> [card] [Migrate from Export API v1 to v3](https://developers.pleo.io/deprecation/legacy-export-api/migrate-from-v1-to-v3.md)
>
> For integrations on `/v1/`. Skip v2 and go directly to v3. The payload structure changes, so check your parsing.

> [card] [Migrate from Export API v0 to v3](https://developers.pleo.io/deprecation/legacy-export-api/migrate-from-v0-to-v3.md)
>
> For integrations on `/v0/`. Skip v1 and v2 and go directly to v3. The payload structure changes, so check your parsing.

## What changes in v3

* The version number in the path changes to `/v3/`.
* The Export Item has more data. You can ignore the extra fields.
* Contra accounts are new in v3. You must map them before you can create an Export Job. See [How to Resolve MISSING\_CONTRA\_ACCOUNTS](https://developers.pleo.io/docs/current/how-tos/accounting-integrations/how-to-resolve-missing-contra-accounts.md).
* The `teamCode` field is removed. Use `team.code` instead.
* Fields that listed fixed values in v0, v1 and v2 are plain strings in v3. Your integration must not fail on a value that it does not know.

For the details, see the guide for your version.
