🆕 Transaction Attachments

📝 Overview

Main Use Case: This allows accounting software, in particular, to automatically retrieve the supporting document already present in the bank account, without needing to ask the user to provide it again.

⚠️ Coverage & Availability

To date, the coverage for this feature is limited. We have currently only implemented this mechanism for Qonto.

🚀 How it works

1. List attachments for a transaction

For all our clients, the list of attachments is available on the get transactions endpoint (v2025 API). Each attachment is listed with an identifier and a file name to recognize it.

Endpoint: GET /v3/aggregation/transactions

Response format:

[
  {
    // ...
    "attachments": [
      {
        "id": "string",
        "file_name": "string"
      }
    ]
  }
]

2. Get the download URL

To obtain the actual download URL of the attachment, a call to a dedicated endpoint is required.

Security Prerequisite: The application must possess the ATTACHMENTS_TRANSACTIONS scope.

Endpoint: GET /v3/aggregation/transactions/{transactionId}/attachments/{attachmentId}

Response format:

{
  "url": "string"
}

Qonto Specifics

To successfully retrieve a Qonto attachment download URL, even if the attachment is listed via the transactions endpoint, the corresponding item must meet the following strict conditions:

Valid Provider IDs: 4108 or 4118 (deprecated Qonto connectors do not work for this feature).
SCA (Strong Customer Authentication): The SCA date on this provider must be > 2026-08-12 13:19.
Item Status Code: 0.

Important: The generated link to download the Qonto attachment is valid for 30 minutes.

API Reference

Check the API Reference for more details on full parameters and schemas: