Bien Sparebank API Access & Open Banking Data

Bien Sparebank is a Norwegian savings bank, and open-banking.io lets you reach its account and transaction data without wrestling with eIDAS certificates or a lengthy PSD2 licensing project. As a certificate-free service covering 2,600+ EU/UK banks, it turns Bien Sparebank access into a few clicks in a web dashboard — while keeping the cryptography firmly in your hands. Whether you bank as a private customer or run a company, this page walks you through connecting once and, if you want, reading the data in code later.

The distinguishing feature is privacy by architecture. open-banking.io is zero-knowledge: an encryption keypair is generated on your own device, and the service only ever holds your public key. Everything you pull from Bien Sparebank is decrypted locally, so no server — not even open-banking.io's — can read your balances or statements.

How to connect Bien Sparebank

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

  1. Sign up for an open-banking.io account.
  2. Set an encryption passphrase; your keys are created locally on your device and never leave it.
  3. In the dashboard, pick Bien Sparebank and choose your account type — both business and personal are supported.
  4. You are redirected to Bien Sparebank's own secure login to approve access under PSD2. You authenticate directly with the bank; open-banking.io never sees your credentials.
  5. Your approved accounts sync back into the dashboard. Bien Sparebank grants consent for up to 180 days, after which you simply re-approve.

Bien Sparebank has no published BIC in our directory, so selecting it by name in the dashboard is the reliable route.

Access your data

Reading data in code is an optional developer step you take after the connection above exists. 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 use the CLI (openbanking accounts, openbanking transactions, openbanking sync), an SDK, or the REST API. Requests authenticate with the X-Api-Key header, and each response is decrypted locally with your private key. The CLI and SDK only read and sync connections that already exist — they never establish one. An API key on its own returns ciphertext; without your private key it stays unreadable.

Pricing is a flat ~EUR 3/month, with no certificate costs.

Is a QWAC or eIDAS certificate required?

No. open-banking.io is certificate-free, so you skip that setup entirely.

Can open-banking.io read my Bien Sparebank data?

No. It holds only your public key; decryption happens on your device.

How long does access last?

Bien Sparebank consent runs up to 180 days per approval, then you re-authorise.

Start at open-banking.io.