OAuth scope: attachment.write
Uploads a single attachment (JPEG, PNG or PDF).
This operation will enable you to link the uploaded attachement to an external transfer (through POST /v2/external_transfers or POST /v2/external_transfers/checkout).
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.
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"
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/attachments \
-H "Content-Type: multipart/form-data" \
-H "Authorization: {Auth}" \
-F file="@path/to/a/file.jpg"
The body is of type object
.
Returns the uploaded attachment.
The response is of type object
.