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.
Multi-Currency in Export API
contraAccount object is returned in the endpoint response of GET https://external.pleo.io/v3/export-items, when the expense is any of the following types and it impacts the account balance:
card_purchasefeecashbackrefundchargebackdirect_reimbursementinvoice_paymentcard_invoiceatm_withdrawalpersonal_spendwallet_topupwallet_unload
Frequently Asked Questions
If a customer has activated multi-currency, can they still access the Export API version 2?
If a customer has activated multi-currency, can they still access the Export API version 2?
GET Get Export Items endpoint returns 400: Bad Request error and displays the following:Can an integration send a request to the Export API version 3 if multi-currency is not enabled?
Can an integration send a request to the Export API version 3 if multi-currency is not enabled?
GET Get Export Items endpoint. If contra accounts are not fully configured, then the endpoint will return status code 400 along with the following response body:What happens to an `in_progress` export job when `400: Bad Request` is returned in the `GET Get Export Items` endpoint?
What happens to an `in_progress` export job when `400: Bad Request` is returned in the `GET Get Export Items` endpoint?
lastUpdatedAt).Export API Version 3 URLs
Production: https://external.pleo.ioStaging: https://external.staging.pleo.io
v3 instead of v2. For example, POST https://external.pleo.io/v3/export-job-events.