Skip to main content
GET
List transactions
Authentication: API key OAuth 2.0
Scope: organization.read Sensitive
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.

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.

Query Parameters

bank_account_id
string

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.

Example:

"018f71db-c635-78b5-b90a-ea05de98c2bf"

iban
string

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.

Example:

"FR7616798000010000005663951"

includes[]
enum<string>[]

Use this query parameter to embed the associated resources (labels, attachments and/or VAT details) of the transactions in the JSON response.

Available options:
vat_details,
labels,
attachments
status[]
enum<string>[]

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;
  • reversed: a transaction that has been reversed after being completed.

When not specified, only completed transactions will be returned.

Available options:
pending,
declined,
completed,
reversed
updated_at_from
string

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).

Example:

"2019-01-10T11:47:53.123Z"

updated_at_to
string

Transactions can be filtered by their updated_at property. This filter can be used in combination with the updated_at_from query parameter to get transactions updated within a specific timeframe. Please use a valid date time format (ISO 8601 for instance).

Example:

"2019-01-10T11:47:53.123Z"

created_at_from
string

Transactions can be filtered by their created_at property. This filter can be used in combination with the created_at_to query parameter to get transactions created within a specific timeframe. Please use a valid date time format (ISO 8601 for instance).

Example:

"2019-01-10T11:47:53.123Z"

created_at_to
string

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 created within a specific timeframe. Please use a valid date time format (ISO 8601 for instance).

Example:

"2019-01-10T11:47:53.123Z"

emitted_at_from
string

Transactions can be filtered by their emitted_at property. This filter can be used 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).

Example:

"2019-01-10T11:47:53.123Z"

emitted_at_to
string

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).

Example:

"2019-01-10T11:47:53.123Z"

settled_at_from
string

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).

Example:

"2019-01-10T11:47:53.123Z"

settled_at_to
string

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).

Example:

"2019-01-10T11:47:53.123Z"

side
enum<string>

Transactions can be filtered by their side property.

Available options:
credit,
debit
operation_type[]
string[]

Transactions can be filtered by their operation_type property.

Example:

"operation_type[]=card&operation_type[]=transfer&operation_type[]=income&operation_type[]=account_remuneration"

with_attachments
boolean

Transactions can be filtered based on the presence of one or more attachments.

sort_by
string
default:settled_at:desc

Sorts transactions, written as property:order.

  • property: settled_at (default), created_at, updated_at or emitted_at.
  • order: asc or desc (default).

Either part can be left out:

  • settled_at is settled_at:desc.
  • :asc is settled_at:asc.
Pattern: ^(created_at|updated_at|settled_at|emitted_at)?(:(asc|desc)?)?$
Example:

"emitted_at:asc"

page
integer
default:1

Returned page (cf. Pagination). Must be an integer of 1 or more, otherwise the API returns a 422. page × per_page can't exceed 10,000. Past that, the API returns a 422 too. To reach older transactions, narrow the date filters.

Required range: x >= 1
per_page
integer
default:100

Number of transactions per page (cf. Pagination). Values outside the 1 to 100 range are clamped to it. A value that isn't an integer, such as 50.0, is treated as 1.

Response

Returns the list of transactions for the specified bank account.

transactions
object[]
meta
object

Metadata for paginated responses