OAuth scope: attachment.write
Uploads a single attachment (JPEG, PNG or PDF) to the transaction identified by the id
path parameter.
In the Qonto app, 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.
The uploaded file will be processed in the background. This means that the created attachment will not be visible immediately.
Bearer authorization header: Bearer <token>
, where <token>
is the access token received from the authorization server at the end of the OAuth 2.0 flow.
Required only for Sandbox API requests; to get one, please sign up to the Developer Portal.
Learn more in Idempotent Requests.
"123e4567-e89b-12d3-a456-426614174000"
"2751a41c-c17f-43f7-bd18-04efa6cd8e30"
You have to specify multipart form data in order to attach the file to the request. When using curl
it will look like that:
curl --request POST \
--url https://thirdparty.qonto.com/v2/transactions/{id}/attachments \
-H "Content-Type: multipart/form-data" \
-H "Authorization: {Auth}" \
-F file="@path/to/a/file.jpg"
The body is of type object
.
Accepts the file and returns a success status code.