/ics/v3/accounts/{id}/transactions

Returns a list of transactions for the account Id given as endpoint parameter. The account Id must first be retrieved in a Get Accounts call.
This API will return a 1426 error if consent is required to access the account.
Note that x-psu-ip-address is required for DNB, Sbanken and SEB. For KLP Banken and SpareBank 1 Østlandet, it is required when requesting transactions older than 90 days.

API Usage Restrictions (PSD2 Compliance):

  • Each unique API call is limited to 4 requests per 24 hours per session.
  • Important: Pagination does NOT count against the same limit. Each unique cursor value has its own separate 4-call counter.
  • This means you can browse through unlimited transaction pages, but can only revisit the same page 4 times within 24 hours.
  • The 24-hour window is a rolling period starting from your first call to that specific operation.
  • New sessions get fresh counters.
Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required
Query Params
string

Provide scope for your request, possible values - (accounts, business-accounts).
Use accounts (default) for retail accounts.
Use business-accounts for business and corporate accounts.

string

Furthest date in the past of requested transaction range. YYYY-MM-DD.
Recommended date range is 1 year as some banks return maximum one year transactions in a request.
Split date range in multiple requests to get transactions more than a year.

string

Most recent date of requested transaction range. YYYY-MM-DD

string

Cursor for pagination. When more transactions are available, the response includes a links array with a link where rel is "next".
Extract the cursor query parameter value from the href URL and pass it here to fetch the next page.

Example: If the response contains:

"links": [{ "rel": "next", "href": "https://sandbox.neonomics.io/.../transactions?cursor=0X4lQV7dZZ4x..." }]

Use cursor=0X4lQV7dZZ4x... in your next request.

Important:

  • Do not pass fromDate and toDate query parameters when using cursor.
  • The cursor is an encrypted opaque string - do not attempt to decode or modify it.
  • Each unique cursor value has its own separate API usage counter, so navigating through different pages does not consume your 4-call limit for previous pages.
string

Accepts "booked" or "pending". By default all transactions are returned.

integer
1 to 50

Number of transactions per page. Must be between 1 and 50. Defaults to 50 if not provided.

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

Additional identifier of the end-user, sent together with x-psu-id to the few banks that need two
identifiers, e.g. the organisation the end-user acts for on business requests, in the format the bank expects.
This parameter is required if x-psu-corporate-id is listed in the bank's requiredPsuHeaders (returned from
the /banks endpoint) for the channel of the request; otherwise it is optional.

Value formats for the banks that use it today:

  • Länsförsäkringar: required in addition to x-psu-id, and both are distinct. x-psu-id carries the
    signing person's personnummer (SSN), type SSSN; x-psu-corporate-id carries the organisationsnummer
    (org number), type SON. Confirmed with the bank: both values must be exactly 12 numeric digits — a
    continuous digit string with no hyphens, spaces, letters, or special characters (e.g. 12345678-0987 is
    not valid). Fewer or more than 12 digits fails validation.
  • Sparebanken Vest / Folio: required on both consent initiation and every subsequent account/transaction
    read, not only at consent time. Carries the 9-digit Norwegian organisation number. x-psu-id is optional
    here and, if sent, must be the authorising person's national identifier — never the organisation number.
  • DNB: send either x-psu-id or x-psu-corporate-id, depending on the customer type. Private (retail)
    customers: send x-psu-id with the 11-digit National Identification Number. Corporate customers: send
    x-psu-corporate-id which is the TX-ident, a DNB-specific ID of 7 characters (2 letters followed by 5 digits)
    that DNB gives the corporate user when they become a DNB corporate client.
  • SEB Sweden: for business account reads, picks the company the end-user acts for. Carries either the
    14-digit SEB corporate id or the 10-digit organisation number. Send it only with the business-accounts
    scope: SEB does not accept it for private accounts. Without it, an end-user who is also a private SEB customer
    gets their private accounts.
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