Flekkefjord Sparebank API Access & Open Banking

Flekkefjord Sparebank customers can bring their account and transaction data into open-banking.io, a certificate-free open-banking service covering 2,600+ EU and UK banks. There is no PSD2 sandbox to register, no eIDAS certificate to buy, and no server that can read your figures: your data is decrypted on your own device with a key only you hold. That combination makes Flekkefjord Sparebank open banking practical for a single account holder, a small finance team, or a developer building on top of Norwegian bank data.

Because open-banking.io is zero-knowledge, its servers only ever store your public key. Everything readable — balances, payees, transaction history — is unlocked locally, so the platform physically cannot see inside your Flekkefjord Sparebank accounts.

How to connect Flekkefjord Sparebank

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 key pair is generated right there on your device.
  2. In the dashboard, search for Flekkefjord Sparebank and choose your account type — business or personal.
  3. You are redirected to Flekkefjord Sparebank's own secure login, where you approve access on the bank's PSD2 consent screen.
  4. Your accounts sync back into the dashboard. Consent lasts up to 180 days, after which you simply re-approve.

That is the whole flow — you authenticate directly with Flekkefjord Sparebank, and open-banking.io never touches your credentials.

Access your data

Once a connection exists, reading it programmatically is an optional developer step. On the Developers page, create an API key and export a credentials.json — it bundles the API key with your private decryption key. From there use the CLI (openbanking accounts, openbanking transactions, openbanking sync), an SDK, or the REST API. Requests carry your key in the X-Api-Key header, and every response is decrypted locally with your own key. Without that private key an API response is only ciphertext, which is exactly why the service can stay zero-knowledge. Note that Flekkefjord Sparebank publishes no BIC here, so identify accounts by their IBAN or account number. At around EUR 3/month, it is a low-cost way to keep Flekkefjord Sparebank data flowing into your own tools.

Do I need an eIDAS certificate?

No. open-banking.io is certificate-free — you approve access directly with Flekkefjord Sparebank and skip the regulatory paperwork entirely.

Can open-banking.io read my transactions?

No. It stores only your public key; decryption happens on your device, so nobody at open-banking.io can see your data.

Can the CLI connect my bank for me?

No. The CLI and SDK only read or sync connections that already exist. Connecting Flekkefjord Sparebank is always done through the dashboard consent flow.

Start at open-banking.io.