Skip to main content
This page describes the requirements that apply to your integration as a whole, beyond any single export or sync workflow. At present there is one: the integration must keep logs and let users download them.

Logs

Bookkeepers need to review exported expenses, see their details and resolve export issues when they occur. To support this, your integration must save information about every Export Job and every Export Item within it. It must also let users download that information as a file.

What the Log File Contains

The downloaded file must contain the following information. Context
  • A snapshot of the configuration parameters and their values at the time of download. See User-Facing Configurations.
  • The Accounting System version, if it applies.
  • The connected Pleo entity, with its company_id.
  • The connected company in the Accounting System.
Export logs For each Export Job, include at least these fields. For each Export Item in the Export Job, include at least these fields. Other logs Record each of the following operations with a timestamp and a success status.
  • Token refresh operations
  • Tags sync operations
  • Tax Codes sync operations
  • Accounts sync operations
  • Vendor sync operations

Retention

Keep each log for 30 days. Delete any log that is older than 30 days automatically.

Where the Data Comes From

Most of the Export Job and Export Item fields come from the values your integration already sends when it updates statuses. Use the same failureReason and failureReasonType values you report to Pleo, so the log and Pleo always agree. See Update Export Items for the values. The export log file above is the log that your integration must let users download. Other pages describe how to log specific operations, and what you must never log. Use them as guidance when you record the “Other logs”. They do not add fields to the export log file.

Never Log Credentials

Do not write tokens or full API Keys to logs, error messages or debug output. If you need an identifier for debugging, keep at most the last 4 characters of an API Key.

Token Refresh and Authentication

Sync Operations

Export Processing