Skip to main content
This guide is for partners who used the Expenses API to build custom export integrations to accounting systems. If you were fetching expense data for other workflows, see Migrate to the Accounting Entries API instead.

​
New to the Export API?

Export Workflow Guide

End-to-end walkthrough of the Export API integration model.

Integration Design

Rules and requirements for each part of an export integration.

Connect Pleo to a Custom API Integration

How to connect Pleo to route exports to your custom integration.

API Scopes

Required scopes: export-jobs:write, export-jobs:read, export-items:read.

OAuth Guide

End-to-end OAuth 2.0 workflow guide for Pleo integrations.

OAuth with Postman

How to configure Postman to authenticate using OAuth and call the Pleo API.

Standalone API Key Guide

End-to-end guide for authenticating with standalone API keys.

Standalone API Keys with Postman

How to make API calls using standalone API keys in Postman.

​
What Changes in Your Integration

The table below gives a quick overview of how each step maps from the Expenses API to the Export API.
StepBefore (Expenses API)After (Export API)
Detect new exportsPoll GET /v1/expenses?status=QUEUEDListen for v1.export.job-created webhook
Start a jobNot applicablePOST /v3/export-job-events with "event": "started"
Fetch itemsGET /v1/expenses?status=QUEUEDGET /v3/export-jobs/{jobId}/items
Process export itemsAt integration’s discretionIntegration design guidelines and workflow guide
Update item statusPUT /v1/expenses with {"status": "EXPORTING"}PUT /v3/export-jobs/{jobId}/items with granular statuses
Complete the exportPUT /v1/expenses with {"status": "EXPORTED"}Update item statuses + POST /v3/export-job-events with "event": "completed"
The following sections cover each change in detail.

​
Detecting New Exports

Before: 
GET /v1/expenses?status=QUEUED
After: Listen for the v1.export.job-created webhook event.

​
Starting a Job

Before: Not applicable. After: Create a started event to claim the job before processing. 
POST https://external.pleo.io/v3/export-job-events
Content-Type: application/json

{
    "event": "started",
    "jobId": "[JOB_ID]"
}

​
Fetching Export Items

Before: 
GET https://openapi.pleo.io/v1/expenses?status=QUEUED
After: 
GET https://external.pleo.io/v3/export-jobs/[JOB_ID]/items

​
Processing Export Items

Before: At integration’s discretion. After: Pleo provides integration design guidelines and a dedicated workflow guide covering bookkeeping methods, accounts mapping, data mapping, attachments, and posting behaviour.

​
Updating Item Status

Before: 
PUT https://openapi.pleo.io/v1/expenses
Content-Type: application/json

{"status": "EXPORTING"}
After: Update individual items with granular statuses (in_progress, successful, failed, or abandoned). 
PUT https://external.pleo.io/v3/export-jobs/[JOB_ID]/items
Content-Type: application/json

[
    {"accountingEntryId": "[ITEM_ID]", "status": "in_progress"}
]

​
Completing the Export

Before: 
PUT https://openapi.pleo.io/v1/expenses
Content-Type: application/json

{"status": "EXPORTED"}
After: Update item statuses to their final state, then create a completed event. 
PUT https://external.pleo.io/v3/export-jobs/[JOB_ID]/items
Content-Type: application/json

[
    {
        "accountingEntryId": "[ITEM_ID]",
        "status": "successful",
        "exportedAt": "2025-07-31T12:48:52.236Z",
        "externalId": "[ENTRY_ID_IN_YOUR_ACCOUNTING_SYSTEM]",
        "externalUrl": "[ENTRY_URL_IN_YOUR_ACCOUNTING_SYSTEM]"
    }
]

POST https://external.pleo.io/v3/export-job-events
Content-Type: application/json

{
    "event": "completed",
    "jobId": "[JOB_ID]"
}

​
Data Model Changes

The table below maps fields from the Expense model to their equivalents in the Export Item model.
  • — : field is not available in the Export Item model
  • * : data is the same but represented differently. See the Export Item API reference for details.
  • ** : resolved entity relationship: the associated data is included directly, removing the need for additional API calls
Expense fieldExport Item equivalent
idaccountingEntryId
employeeIduser.id
employeeCodeuser.code
departmentIdteam.id
performedAtdate
amountOriginal—
amountSettledamount *
notenote
typetype *
accountIdaccountingEntryLines[].account.id
taxCodeIdaccountingEntryLines[].tax.id
createdAtdate **
updatedAtdate **
deletedAt—
tagIds[].idaccountingEntryLines[].tags[].id
tagIds[].tagGroupIdaccountingEntryLines[].tags[].groupCode **
receiptIds[]files[] **
settledExpenseIds[]additionalInformation.reconciledEntries[]
status—
supplier.CIFsupplier.taxIdentifier
supplier.documentNumber—
cardTransaction.state—
cardTransaction.authorizedAt—
cardTransaction.settledAtdate
cardTransaction.reversedAt—
cardTransaction.merchant.idvendor.id
cardTransaction.merchant.namevendor.name
lines[].amountSettledaccountingEntryLines[].lineAmount
lines[].accountIdaccountingEntryLines[].account.id
lines[].taxCodeIdaccountingEntryLines[].tax.id
lines[].tagIds[]accountingEntryLines[].tags[].id