Nordigen Account Information Services API
Agent-ready OpenAPI document · curated by JenticFinanceBankingbearer28 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Aggregate European bank accounts, balances, and transactions across 2,000-plus institutions through Nordigen's PSD2 API on behalf of consented end users.
Use for: List the banking institutions Nordigen supports in Germany, Create a requisition so a user can link their UK bank account, Get all accounts an end user has linked through Nordigen, Pull last 90 days of transactions on a linked account
Not supported: Does not handle card issuing, KYC document verification, or non-European banks - use for European PSD2 account information aggregation and payment status reads only.
Jentic publishes the only available OpenAPI specification for Nordigen Account Information Services API, keeping it validated and agent-ready. Nordigen, now operated as GoCardless Bank Account Data, provides PSD2-compliant Account Information Services across more than 2,000 European banks via a single API. The API exposes institutions, end-user agreements, requisitions for consent, accounts with balances, transactions, and account details, plus premium transaction endpoints and a payments preview. Fintechs, lenders, and personal finance apps use it to aggregate account data across the EU and UK without negotiating per-bank integrations.
Install Jentic One Beta
Connect the Nordigen Account Information Services API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Nordigen Account Information Services API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fnordigen.com%2Fnordigen" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fnordigen.com%2Fnordigen" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Nordigen Account Information Services API.
List supported banking institutions across European countries
Create end-user agreements that scope which data the customer consents to share
Generate requisitions that drive the consent redirect flow
List accounts that an end user has linked through a completed requisition
Pull balances, account details, and transactions for a linked account
Access premium transaction data with extended history beyond PSD2 minimums
Read payment status for previously initiated payments
Use Cases
Patterns agents use Nordigen Account Information Services API for, with concrete tasks.
★ Pan-European account aggregation
Lenders and PFM apps that need consistent account data across the EU use Nordigen to avoid integrating each national bank individually. /api/v2/institutions/ returns the supported banks per country, /agreements/enduser/ creates the consent envelope, and /requisitions/ drives the redirect. Once linked, /accounts/{id}/transactions returns ISO 20022-style transactions whose schema matches across banks.
List institutions for country DE, then create an end-user agreement and requisition that lets the user link their Deutsche Bank account
Lending underwriting from bank data
Lenders running affordability checks pull 90-180 days of bank transactions through Nordigen to verify income and recurring expenses without requesting paper statements. /api/v2/accounts/{id}/transactions/ and the /accounts/premium/{id}/transactions/ premium endpoint return the categorisable history that an underwriting model needs to score affordability.
Pull /api/v2/accounts/{id}/transactions/ for the last 90 days and tag salary credits and rent debits for affordability scoring
Subscription dunning recovery
B2B SaaS dunning workflows can confirm that a customer's bank account has actually received expected income before retrying a failed direct debit. With consented bank data via Nordigen, the system can detect that payroll just landed and reschedule the retry for the next morning rather than burning bank fees on doomed retries.
Check /accounts/{id}/balances and /accounts/{id}/transactions for a salary credit before scheduling a direct debit retry
AI agent for personal finance
An AI personal finance assistant covering EU users can use Jentic to discover the Nordigen requisition flow and account endpoints, then return categorised spending across accounts. The agent searches Jentic for 'list bank transactions', loads the account transactions schema, and executes - no per-bank wiring.
Through Jentic, search 'list bank transactions', load /api/v2/accounts/{id}/transactions/, and execute with the user's linked account ID
Key Endpoints
28 endpoints — jentic publishes the only available openapi specification for nordigen account information services api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/api/v2/institutions/
List supported European banks
POST
/api/v2/agreements/enduser/
Create an end-user consent agreement
POST
/api/v2/requisitions/
Create a requisition that drives the consent redirect
GET
/api/v2/accounts/{id}/
Read account metadata for a linked account
GET
/api/v2/accounts/{id}/balances/
Read balances on a linked account
GET
/api/v2/accounts/{id}/transactions/
List transactions on a linked account
GET
/api/v2/accounts/premium/{id}/transactions/
Premium extended transaction history
GET
/api/v2/institutions/
List supported European banks
POST
/api/v2/agreements/enduser/
Create an end-user consent agreement
POST
/api/v2/requisitions/
Create a requisition that drives the consent redirect
GET
/api/v2/accounts/{id}/
Read account metadata for a linked account
GET
/api/v2/accounts/{id}/balances/
Read balances on a linked account
GET
/api/v2/accounts/{id}/transactions/
List transactions on a linked account
GET
/api/v2/accounts/premium/{id}/transactions/
Premium extended transaction history
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Nordigen by hand means exchanging your secret_id and secret_key for a JWT, refreshing it against ob.nordigen.com, and threading the bearer token through requisition and account calls yourself. Through Jentic you install once, import the Nordigen Account Information Services API from the API Directory, store the credentials once, and your agent calls it.
Permission scoping
Nordigen puts the account id in the URL path (/api/v2/accounts/{id}/...), so a rule can pin your agent to one account for balances and transactions. You choose the operations it may call, so creating end-user agreements or requisitions is not included unless you add it.
Credential isolation
Your Nordigen secret_id, secret_key, and refreshed JWT are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'list bank transactions' or 'find an institution', and Jentic returns the matching Nordigen operation with its input schema so the agent calls /api/v2/accounts/{id}/transactions/ without browsing the PSD2 docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Nordigen Account Information Services API through Jentic.
Why is there no official OpenAPI spec for Nordigen Account Information Services API?
Nordigen does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Nordigen Account Information Services API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.
What authentication does the Nordigen API use?
Nordigen uses HTTP bearer authentication with JWTs. You exchange a secret_id and secret_key for an access token that you pass in the Authorization header. Through Jentic, the JWT is held in the encrypted vault and refreshed automatically by the runtime.
Can I list European banks supported by Nordigen?
Yes. GET /api/v2/institutions/ returns institutions filtered by country code; GET /api/v2/institutions/{id}/ returns details for a single institution including supported countries and logo. Use the country filter to scope the bank list shown in your linking UI.
What are the rate limits for the Nordigen API?
Under PSD2, Nordigen permits up to four unattended polls per linked account per day plus unlimited calls when the user is present. The free tier covers reasonable production volume; cache /accounts/{id}/transactions/ responses for 6 hours to stay within the daily budget.
How do I link a user's bank account through Nordigen via Jentic?
Install with pip install jentic, then search 'create a Nordigen requisition', load POST /api/v2/requisitions/, and execute with the institution_id and a redirect URL. Send the user to the returned link; once they complete consent, /api/v2/accounts/{id}/ returns the linked accounts.
Does the Nordigen API include premium transaction data?
Yes. /api/v2/accounts/premium/{id}/transactions/ returns extended history beyond the PSD2-mandated 90 days, where the underlying bank exposes it. Premium endpoints are gated by Nordigen plan; check your contract before relying on them.
Can I initiate payments through Nordigen?
The spec exposes /api/v2/payments/ read endpoints for payment status. Payment initiation is offered as a separate Nordigen product line; if you need PIS, contact Nordigen to enable PIS endpoints on your account beyond what this AIS spec covers.
Can I limit what my agent is allowed to do with the Nordigen Account Information Services API?
Yes. Because you run Jentic One yourself, your own rules decide which Nordigen operations and credentials the agent may use. Since Nordigen puts the account id in the URL path (for example /api/v2/accounts/{id}/balances/ and /api/v2/accounts/{id}/transactions/), a rule can pin the agent to a single account for balance and transaction reads. You also choose the operation set, so creating end-user agreements or requisitions stays off unless you explicitly grant it.
GET STARTED