---
title: "Upload attachment to a transaction"
method: POST
path: "/v2/transactions/{id}/attachments"
tags: ["Attachments in Transactions"]
---

# Upload attachment to a transaction

`POST /v2/transactions/{id}/attachments`

OAuth scope: `attachment.write`

---

Upload an attachment to a transaction

---

This endpoint allows you to upload an attachment to a transaction.

Inside Qonto, attachments are files uploaded onto transactions by users. Attachments typically correspond to the *invoice* or *receipt*, and are used to justify the transactions from a bookkeeping standpoint.

Probative attachment is another version of attachment, compliant with [PAdES](https://en.wikipedia.org/wiki/PAdES) standard.

**Important**: for security reasons, the `url` you retrieve for each Attachment is only valid for 30 minutes. If you need to download the file after more than 30 minutes, you will need to perform another authenticated call in order to generate a new download URL.


<!-- theme: info -->
> The uploaded file will be processed in the background. This means that the created attachment will not be visible immediately.

## Path parameters

- `id` string, uuid, required

## Headers

- `X-Qonto-Idempotency-Key` string, uuid
- `X-Qonto-Staging-Token` string

## Response `200`

accepts the file and returns a success status code

## Other responses

- `400` — returns a bad request error
- `401` — returns an unauthorized error
- `403` — returns a forbidden error
- `404` — returns a not found error

---

[API](https://skmtc.net/hiit-consulting-fr/apis/qonto.md) · [All operations](https://skmtc.net/hiit-consulting-fr/apis/qonto/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/hiit-consulting-fr/qonto/versions/25208d6f9deb/schema)