First, you'll need to get your
token from the Nordigen's Open Banking Portal.
N.B. If you are not a verified client (passed manual KYC verification), please skip this step.
token from Step 1 as
Second, you need to create an agreement and pass the
end user ID (unique ID defined by you) as the UUID and
agreement version ID retrieved in the response above.
Third, you need to expose agreement to an end user and require action from the end user for agreeing on the terms. Once the end user agrees to terms, execute the following command by providing
user agent and
First, you need to create a requisition which is a collection of inputs for creating links and retrieving accounts. For all requisition API requests you will need to provide access token from Step 1 as
YOUR_TOKEN. You are also required to define the
end user ID (unique end user ID defined by you), a
reference ID (additional layer of unique ID defined by you) and a
redirect link where an end user will be redirected after finishing authentication in ASPSP.
N.B. use the same end user ID from Step 2 if it applies to you.
Second, create a redirect link for the end user to ASPSP. You need to provide
aspsp_id which is the unique identifier of the end users bank. See guide on how to build an UI for a user to select a bank and how to find appropriate
Once a user is redirected back to the link provided in Step 3, users' bank accounts can be listed. Pass
requisition ID to view accounts.
To access account information and transactions, you need to pass
account ID. Each account need to be queried separately.
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