Authorizations
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.
Headers
Required only for Sandbox API requests; to get one, please sign up to the Developer Portal.
Body
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 --location --request POST 'https://thirdparty.qonto.com/supplier_invoices/bulk' \
--form 'supplier_invoices[][file]=@"/path/to/file1.png"' \
--form 'supplier_invoices[][idempotency_key]="4d5418bb-bd0d-4df4-865c-c07afab8bb48"' \
--form 'supplier_invoices[][file]=@"/path/to/file2.png"' \
--form 'supplier_invoices[][idempotency_key]="4d5418bb-bd0d-4df4-865c-c07afab8bb49"' \
--form 'source="pay_by_invoice"' \
--form 'meta="{\"integration_type\":\"dropbox\",\"connector\":\"grover\"}"' \
--form 'skip_attachment_matcher=true'- Option 1
- Option 2
pay_by_invoice, supplier_invoices, integration, transaction_attachment, generic_upload "pay_by_invoice"
Field used to append metadata to supplier invoices.
If true, skips the attachment matcher step for all invoices in the bulk request.
false
Response
Returns the supplier invoices created.
This endpoint will always return a 200 regardless if there are any errors. Clients must ensure to check the errors property in order to confirm if all operations were successful.
A 400 will be returned only if the whole request fails.