GET
/
v2
/
transactions
curl --request GET \
  --url https://thirdparty.qonto.com/v2/transactions \
  --header 'Authorization: Bearer <token>'
{
  "transactions": [
    {
      "transaction_id": "super-transaction-7468",
      "amount": 0.43,
      "amount_cents": 43,
      "settled_balance": 111.1,
      "settled_balance_cents": 11110,
      "attachment_ids": [],
      "local_amount": 0.43,
      "local_amount_cents": 43,
      "side": "debit",
      "operation_type": "transfer",
      "currency": "EUR",
      "local_currency": "EUR",
      "label": "Ferry-Purdy",
      "settled_at": "2021-03-03T16:06:38.000Z",
      "emitted_at": "2021-02-25T16:22:37.000Z",
      "updated_at": "2020-12-12T19:52:10.000Z",
      "status": "completed",
      "note": "Rhea Ernser",
      "reference": null,
      "vat_amount": null,
      "vat_amount_cents": null,
      "vat_rate": null,
      "initiator_id": "ccdcef78-1aa1-4d44-b991-b10005a4ad1a",
      "label_ids": [
        "6450e541-0a6f-4153-a46e-34d98848e280"
      ],
      "attachment_lost": false,
      "attachment_required": true,
      "card_last_digits": "1234",
      "category": "gas_station",
      "id": "df346899-3595-421a-8b26-f9d9616ce496",
      "subject_type": "transfer",
      "transfer": {
        "counterparty_account_number": "NL93RABO3730976796",
        "counterparty_account_number_format": "IBAN",
        "counterparty_bank_identifier": "RABO",
        "counterparty_bank_identifier_format": "SWIFT_BIC"
      }
    }
  ],
  "meta": {
    "current_page": 1,
    "next_page": null,
    "prev_page": null,
    "total_pages": 1,
    "total_count": 1,
    "per_page": 100
  }
}

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. <br>Possible values: <br>- pending: a transaction that is processing and has impacted the bank account's auth_balance but not its balance;<br>- declined: a transaction that has been declined;<br>- completed: a transaction that is completed, and has impacted the bank account's balance.

Available options:
pending,
declined,
completed
​
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_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"

​
emitted_at_from
string

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

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"

​
with_attachments
boolean

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

​
sort_by
string
default:`settled_at:desc`

Transactions can be sorted by a specific property and order. <br>👉 Property: updated_at, settled_at or emitted_at <br>👉 Order: asc (Ascending) / desc (Descending)

​
page
string

Returned page (cf. Pagination).

​
per_page
string

Number of transactions per page (cf. Pagination).

Response

200
application/json
Returns the list of transactions for the specified bank account.

The response is of type object.