OAuth scope: organization.read
Retrieves the list of transactions for the bank account identified by the bank_account_id / iban query parameter.
You can filter (ex: only retrieve the latest transactions) and sort this list by using query parameters 👇
All transactions visible in Qonto’s UI can be retrieved, as of API V2.
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.
id of the bank account for which transactions will be retrieved. Use /v2/organization to get this parameter. If both bank_account_id and iban are specified, bank_account_id takes precedence.
"018f71db-c635-78b5-b90a-ea05de98c2bf"
IBAN of the bank account for which transactions will be retrieved. Use /v2/organization to get this parameter. If both bank_account_id and iban are specified, bank_account_id takes precedence.
"FR7616798000010000005663951"
Use this query parameter to embed the associated resources (labels, attachments and/or VAT details) of the transactions in the JSON response.
vat_details, labels, attachments Transactions can be filtered by their status property.
Possible values:
pending: a transaction that is processing and has impacted the bank account's auth_balance but not its balance;declined: a transaction that has been declined;completed: a transaction that is completed, and has impacted the bank account's balance.pending, declined, completed Transactions can be filtered by their updated_at property. This filter can be used in combination with the updated_at_to query parameter to get transactions updated within a specific timeframe. Please use a valid date time format (ISO 8601 for instance).
"2019-01-10T11:47:53.123Z"
Transactions can be filtered by their updated_at property. This filter can be used in combination with the updated_at_to query parameter to get transactions updated within a specific timeframe. Please use a valid date time format (ISO 8601 for instance).
"2019-01-10T11:47:53.123Z"
Transactions can be filtered by their created_at property. Can be use in combination with the created_at_to query parameter to get transactions emitted within a specific timeframe. Please use a valid date time format (ISO 8601 for instance).
"2019-01-10T11:47:53.123Z"
Transactions can be filtered by their created_at property. This filter can be used in combination with the created_at_from query parameter to get transactions emitted within a specific timeframe. Please use a valid date time format (ISO 8601 for instance).
"2019-01-10T11:47:53.123Z"
Transactions can be filtered by their emitted_at property. Can be use in combination with the emitted_at_to query parameter to get transactions emitted within a specific timeframe. Please use a valid date time format (ISO 8601 for instance).
"2019-01-10T11:47:53.123Z"
Transactions can be filtered by their emitted_at property. This filter can be used in combination with the emitted_at_from query parameter to get transactions emitted within a specific timeframe. Please use a valid date time format (ISO 8601 for instance).
"2019-01-10T11:47:53.123Z"
Transactions can be filtered by their settled_at property. This filter can be used in combination with the settled_at_to query parameter to get transactions settled within a specific timeframe. Please use a valid date time format (ISO 8601 for instance).
"2019-01-10T11:47:53.123Z"
Transactions can be filtered by their settled_at property. This filter can be used in combination with the settled_at_from query parameter to get transactions settled within a specific timeframe. Please use a valid date time format (ISO 8601 for instance).
"2019-01-10T11:47:53.123Z"
Transactions can be filtered by their side property.
credit, debit Transactions can be filtered by their operation_type property.
"operation_type[]=card&operation_type[]=transfer&operation_type[]=income&operation_type[]=account_remuneration"
Transactions can be filtered based on the presence of one or more attachments.
true, false Transactions can be sorted by a specific property and order.
Property: created_at, updated_at, settled_at or emitted_at
Order: asc (Ascending) / desc (Descending)
Returned page (cf. Pagination).
Number of transactions per page (cf. Pagination).