/ics/v3/accounts/{iban}/transactions/categorized

Beta: This endpoint is currently in beta. Its request and response contract may change without notice.

Returns categorized transactions for the provided account IBAN.

This endpoint enriches account transactions with categorization metadata:

  • reason: latest categorization reason text
  • transactionCategories: category labels assigned by the categorization profile

Pagination is page-based and controlled through the page and pageSize query parameters.

Results can be narrowed (AND-combined) by a value-date window, amount range, direction and category. The value-date window is mandatory and bounded: when omitted it defaults to the last 30 days, and the requested span may not exceed 90 days.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required

IBAN of the account for which categorized transactions should be fetched.

Query Params
integer
≥ 0
Defaults to 0

Zero-based page index. Default is 0.

integer
1 to 50
Defaults to 20

Number of transactions per page. Default is 20.

date

Inclusive lower bound on the transaction value date (ISO 8601 yyyy-MM-dd). The value-date window is mandatory and bounded: when omitted it defaults to 30 days before dateTo (or today), and the requested span may not exceed 90 days (otherwise 400). The window is resolved against the current UTC date. Transactions without a value date fall outside every window and are not returned.

date

Inclusive upper bound on the transaction value date (ISO 8601 yyyy-MM-dd). Defaults to today (UTC) when omitted. The window (dateFrom..dateTo) may not exceed 90 days.

number
≥ 0

Inclusive lower bound on the transaction amount.

number
≥ 0

Inclusive upper bound on the transaction amount.

string
enum

Filter by ISO 20022 direction, matched case-insensitively. Values: "CRDT" (credit) or "DBIT" (debit).

Allowed:
categoryIds
array of strings

Comma-separated category ids (max 20). Matches transactions categorized (by the requesting profile) in ANY of the given categories.

categoryIds
Headers
string
required

The session Id returned in the response body when this session was created.

string
required

String that uniquely identifies a single end-user or device.

string
required

The IP Address of the end-user (PSU), which must be provided if the PSU actively requests information.
If this value is not provided, then the call will count towards the number of TPP calls without PSU interaction.
Leave it empty if the end user is not actively requesting account information, such as during automatic background updates.
Provided in either IPv4 or IPv6 format.

string

Identifier of the end-user, passed as the base64-encoded value of an encrypted string following
the guidelines given in Documentation > Development > Sensitive end-user data.
Depending on the channel of the request, this is the identifier of the person or of the organisation.
This parameter is required if x-psu-id is listed in the bank's requiredPsuHeaders (returned from the /banks
endpoint) for the channel of the request, or if the bank's 'personalIdentificationRequired' is "true".

string

The host where the request is originating from.
If you are using end to end encryption from our developer portal then this header is mandatory.

string

The request originating date.
If you are using end to end encryption from our developer portal then this header is mandatory.

string

The signature header consisting of the signature string
If you are using end to end encryption from our developer portal then this header is mandatory.

Responses

Language
Credentials
Bearer
JWT
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json