Skip to main content

Get account transactions

GET 
/v1/accounts/:id/transactions

It is possible to filter the transactions by using query parameters:

  • bookingStatus can be used to get only booked transactions, only pending transactions, or both/all transactions.

  • dateFrom and dateTo is used to get transactions within a given timeframe. These parameters are optional, but recomended to use because increases resilience to change with the ASPSP systems and increases performance.

Note that dateFrom is required, and if omitted a default value will be used.

Parameters offset and limit is used for pagination. It is recomended to follow the "next" and "previous" links from the response for subsequent requests. Offset is the offset from the first transaction in the query and limit is the max amount of transactions to return. These parameters are also recomended to use for the same reason as dateFrom and dateTo.

For optimal performance it is recommended to keep the limit to a number between 100 and 200.

In any case the "next" and "previous" links will be generated to promote performance.

Requests without the PSU present is allowed for tranactions within the last 90 days. Limited to 4 calls within a 24 hour period, requiring a PSU consent that is no more than 180 days old.

Example:

This request gets the first 10 transactions for the 1st and 2nd of January 2024:

https://openbanking.paretobank.no/api/v1/accounts/enc!!encoded-account-reference/transactions?bookingStatus=both&dateFrom=2024-01-01&dateTo=2024-01-02&offset=0&limit=10

To get the next 10 transactions change the offset to 10 (so you skip the first 10 you already got), but keep the limit at 10 because you still want 10 transactions:

https://openbanking.paretobank.no/api/v1/accounts/enc!!encoded-account-reference/transactions?bookingStatus=both&dateFrom=2024-01-01&dateTo=2024-01-02&offset=10&limit=10

See XS2A Framework Implementation Guidelines, Section 6.6.5 for additional details.

Request​

Responses​

OK