N26 (Denmark) API Access — Open Banking Without Certificates

Reaching your N26 account data in Denmark usually means wrestling with PSD2 certificates, eIDAS registration, and sandbox paperwork. open-banking.io removes all of that. It links N26 alongside 2,600+ other EU and UK institutions, and everything your account returns is decrypted locally with an encryption key that only you hold — the service never sees it. Whether you keep a personal N26 account or run a business one, the same flow applies, and both account types are supported.

How to connect N26

Connecting happens entirely inside the open-banking.io dashboard — there is no API call, code, or key involved in this step.

  1. Sign up for open-banking.io and open the web dashboard.
  2. Set your encryption passphrase. Your cryptographic keys are generated right there on your own device, so the private key never leaves it.
  3. In the dashboard, search for N26 and choose your account type — business or personal.
  4. You are redirected to N26's own secure login, where you approve access on the bank's official consent screen (standard PSD2 authorisation). A single consent stays valid for up to 180 days before you re-approve.
  5. Your accounts and transactions sync back into the dashboard, ready to view.

Because N26 does not publish a fixed BIC for this route, none is required — selecting the bank by name is enough.

Access your data

Once N26 is connected, reading the data programmatically is an optional developer step. On the Developers page, create an API key and export a credentials.json — it bundles the API key together with your private decryption key. From there use the CLI (openbanking accounts, openbanking transactions, openbanking sync), an SDK, or the REST API. Every request carries the X-Api-Key header, and every response is decrypted locally with your own key. Note that the CLI and SDK only read and sync connections that already exist — there is no connect command. An API key on its own returns ciphertext; without your private key it stays unreadable.

FAQ

Do I need an eIDAS certificate for N26?

No. open-banking.io is certificate-free. You authorise access directly on N26's consent screen, so no QWAC or QSEAL setup is needed.

Can open-banking.io read my N26 transactions?

No. The platform is zero-knowledge and stores only your public key. Data is decrypted on your device with a key that never leaves it.

How much does it cost?

Around EUR 3 per month, covering N26 and every other supported bank on your account.

Ready to start? Visit open-banking.io.