Spareskillingsbanken API Access & Open Banking Data

Spareskillingsbanken customers in Kristiansand can bring their business and personal accounts into a single, developer-friendly workspace through open-banking.io. Instead of wrestling with eIDAS certificates or bank-specific sandboxes, you approve read access once and let open-banking.io keep your balances and transactions in sync — encrypted the whole way, with a decryption key that never leaves your device.

Because open-banking.io is zero-knowledge, its servers only ever hold your public key. Everything you eventually read back is decrypted locally, so no third party — including open-banking.io itself — can see inside your Spareskillingsbanken data.

How to connect Spareskillingsbanken

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

  1. Sign up for open-banking.io and set your encryption passphrase. Your keys are generated right there on your own device.
  2. In the dashboard, search for and select Spareskillingsbanken, then choose the account type you want to link — business or personal.
  3. You are redirected to Spareskillingsbanken's own secure login and consent screen, where you approve access under PSD2. open-banking.io never sees your bank credentials.
  4. Your approved accounts sync back into the dashboard, ready to view. Each consent lasts up to 180 days, after which you simply re-approve on the bank's screen.

Note that Spareskillingsbanken has no published BIC in our reference data, so selecting it by name in the dashboard is the reliable path.

Access your data

Once a connection exists, reading it programmatically is an optional developer step. Open 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.

Every request authenticates with the X-Api-Key header, and every response is decrypted locally with your own key. An API key alone only ever returns ciphertext — without your private key it stays unreadable. The CLI and SDK read and sync existing connections; they never create one.

Does open-banking.io need an eIDAS certificate?

No. It is certificate-free — you approve access on Spareskillingsbanken's consent screen, with nothing to install or provision.

Yes. Both account types are supported; add each one separately in the dashboard.

What does it cost?

Around EUR 3 per month for full access to your synced accounts and the developer tools.

Ready to start? Head to open-banking.io.