Skip to main content
GET
Get Bulk Transfer
Authentication: API key OAuth 2.0
Scope: organization.read Sensitive
Returns a simple JSON response with job-level status and per-transfer details. If there was a failure to create one of the transfers, you should be able to identify which transfer that was based on the client_transfer_id value provided. This makes it easy to pinpoint the exact transfer and property that caused the issue, allowing for quick troubleshooting and resolution. The status of the transfer result does not correspond to the actual transfer status. A transfer can be created but fail once Qonto tried to process it. Use the /v2/sepa/transfers?ids[]=1&ids[]=2&ids[]=n resource to fetch the actual transfers. You can filter up to 100 transfer IDs at a time.

Authorizations

Authorization
string
header
required

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

X-Qonto-Staging-Token
string

Required only for Sandbox API requests; to get one, please sign up to the Developer Portal.

Path Parameters

id
string<uuid>
required

Unique identifier of the bulk transfer.

Response

Successfully retrieved the job status

bulk_transfer
object
required