GET Transactions
Endpoint: GET /psus/{psuId}/aspsps/{aspspId}/accounts/{accountId}/transactions
Base URL: /xs2a/routingservice/services/ob/ais/v3
This endpoint is used to retrieve the balances of an account of a PSU.
Data model
| Request | Response (click to enlarge) |
 |  |
GET Download Transactions
Endpoint: GET /download/psus/{psuId}/aspsps/{aspspId}/accounts/{accountId}/transactions
Base URL: /xs2a/routingservice/services/ob/ais/v3
Some banks do not provide paginated transactions response. In those cases it isn’t possible to predict the number of transactions to be received in response of a GET transactions request. Even if the bank is supporting paginated responses it might be possible that response of the GET transactions request contains a download link only and no transactions, if the number of transactions is considered too high. In this cases or if the bank isn’t giving the response (instead of JSON in CAMT format for example), the Open Banking Service response on the GET transactions will have a download link instead of a set of transactions.
By calling that download link, the response will be given in a streamed JSON structure starting the stream of transactions already before all transactions are downloaded from the ASPSP. If the bank provides the transactions in a non-JSON format the transactions are converted to JSON on the fly.
Data model
| Request | Response |
 | The JSON structure of the response to this request is the same as it is for GET transactions. The only difference is that there will be no MetaData and no links like First, Prev, Next, Last or Download be contained. |