Quickstart Guide

This document explains how to jump start your integration with the Account Information API by using Postman.

Step 1: Get Access Token

First, you'll need to get your token from the Nordigen's Open Banking Portal.

Step 2: Import Postman Collection

To import a collection select Import / Link and enter following link https://ob.nordigen.com/api/swagger.json

Step 3: Choose a Bank

Use aspsps / GET aspsps list endpoint to get a list of all avialable ASPSPs (banks) in a given country. You will need to:
- first, select "No Auth" under Auth TYPE and, second, in the Header provide a KEY "Authorization" and VALUE "Token YOUR_TOKEN" where provide YOUR_TOKEN from Step 1;
- provide a two letter coutry code (ISO 3166) as VALUE for country KEY.

ID for the chosen bank will be used in the following steps (referenced as aspsp_id).


Step 4: Create end user agreement

N.B. Use this step only if you want to specify length of transaction history you want to retrieve. If you skip this step, by default 90 days of transaction history will be retrieved.

Use agreements / enduser / POST agreements endusers create endpoint to create end user agreement. To create an agreement in request body you should pass:
- pass - max historical days as length of the transaction history to be retrieved;
- the end user ID (unique ID defined by you) as the UUID;
- aspsp_id from Step 3;
- delete agreement_version if you have not beed assigned an individual ageement version (applies only to Enteprise clients).


Use requisitions / POST requisitons create endpoint to create a requisition. In the request body you need to provide:
- end user ID (unique end user ID defined by you), a reference ID (additional layer of unique ID defined by you). NB If you didn't skip Step 4 end user ID has to match one provided in Step 4;
- redirect link where an end user will be redirected after finishing authentication in ASPSP;
- agreements ID from Step 4 or leave brackets empty if you skipped that step.

N.B. use the same end user ID from Step 4 if it applies to you.


Second, use requisitions / id / POST requisitons links endpoint to create a redirect link for the end user to ASPSP. In the rquest body you need to provide aspsp_id from Step 3 (it should match aspsp_id from Step 4 if you did not skip it).


Step 6: List accounts

Once a user is redirected back to the link provided in Step 5, use requisitions / id / GET requisitons read endpoint to list users' bank accounts. Pass requisition ID in request body to view accounts.


Step 7: Access accounts, balances and transactions

There are three seperate endpoints for accessing account details, balances and transactions. See account/{id} to view respective endpoints.

In this quickstart we will showcase accounts/{od} GET Access account transactions endpoint, where you need to pass account ID (see "accounts" from output of Step 6) to access transaction information. Each account needs to be queried separately.


What's next.

Congratulations - you now can connect to end user bank accounts and access raw account and transaction data. To learn more about the output data structures and see more details behind the keys, please visit accounts and transactions.

Once you’re ready to extract more value from the raw account information, take a look at our premium products - Transaction Categorisation and Insights