Knab API Access & Open Banking Data Integration

Knab is a Dutch online bank built for entrepreneurs and everyday savers, and open-banking.io gives you a clean, private way to reach its data. Instead of wrestling with bank-specific PSD2 sandboxes, eIDAS certificates, or QWAC onboarding, you link Knab once and read your balances and transactions through a single interface. open-banking.io covers 2,600+ European banks, so Knab sits alongside the rest of your accounts under one roof.

The defining trait is privacy. open-banking.io is zero-knowledge: your encryption keys are generated on your own device from a passphrase only you know, and the service stores nothing but your public key. Every record you pull is decrypted locally, so the servers can never read your Knab data in the clear.

How to connect Knab

Connecting happens entirely in 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 set your encryption passphrase. Your private key is created locally and never leaves your device.
  2. In the dashboard, search for Knab (BIC KNABNL2H) and choose your account type — Knab supports both business and personal accounts.
  3. You are redirected to Knab's own secure login, where you approve the PSD2 consent directly on the bank's screen. open-banking.io never sees your Knab credentials.
  4. Your accounts sync back into the dashboard. A single consent stays valid for up to 180 days before Knab asks you to renew it.

Access your data

Once Knab is connected, reading the data programmatically is an optional developer step. On the Developers page, create an API key and export a credentials.json — this bundles the API key together with your private decryption key. From there you can use the CLI (openbanking accounts, openbanking transactions, openbanking sync), an SDK, or the REST API directly.

Requests authenticate with the X-Api-Key header, and every response is decrypted locally with your own key. That design means an API key alone is useless to anyone else: without your private key, they only ever receive ciphertext.

All of this runs for roughly EUR 3/month, flat.

Do I need an eIDAS certificate for Knab?

No. open-banking.io is certificate-free — it handles the regulated PSD2 access layer, so you skip QWAC/QSEAL onboarding entirely.

Can open-banking.io read my Knab transactions?

No. It holds only your public key. Data is encrypted for you and decrypted on your device, so the service cannot see your balances.

Does connecting Knab require writing code?

No. Linking is done in the dashboard via Knab's own consent screen. The CLI and API are only for reading data you've already connected.

Start at open-banking.io.