Melhusbanken API Access & Open Banking Data

Pulling your Melhusbanken balances and transactions into your own tools used to mean chasing PSD2 certificates and running a licensed API integration. open-banking.io removes all of that. It is a certificate-free, zero-knowledge bridge to 2,600+ EU and UK banks, and Melhusbanken — the savings bank rooted in Melhus, Trøndelag — is one of them. Both business and personal accounts are supported, and a single consent stays valid for up to 180 days before you refresh it.

The difference that matters: your account data is encrypted the moment it leaves the bank and is only ever decrypted on your own device with a key that never leaves you. open-banking.io holds your public key and nothing more, so it physically cannot read what it stores for you.

How to connect Melhusbanken

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 open-banking.io and set your encryption passphrase. Your key pair is generated locally on your device at this point.
  2. In the dashboard, search for Melhusbanken and choose the account type you want to link — business or personal.
  3. You are redirected to Melhusbanken's own secure login, where you approve access on the bank's PSD2 consent screen. Your credentials are only ever entered at the bank.
  4. Once approved, your Melhusbanken accounts sync into your dashboard, and stay connected for the 180-day consent window.

Melhusbanken has no BIC listed here, but you never need one — you select the bank by name in the dashboard.

Access your data

Want the data programmatically? That is an optional developer step, taken after the connection above exists. On the Developers page, create an API key and export a credentials.json — it bundles your 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 directly. Every request carries your key in the X-Api-Key header, and each response is decrypted locally with your private key. The API key alone only ever returns ciphertext — the readable data exists only on your machine.

There is no connect command: the CLI and SDK read and sync connections you already made in the dashboard.

All of this runs for around EUR 3 per month.

Does open-banking.io ever see my Melhusbanken data?

No. It is zero-knowledge — it stores only your public key and encrypted blobs. Decryption happens on your device with a key only you hold.

Do I need a PSD2 certificate for Melhusbanken?

No. The service is certificate-free; you approve access on Melhusbanken's own consent screen and nothing else is required.

How long does my Melhusbanken connection last?

Up to 180 days per consent. When it expires, reconnect in the dashboard to continue syncing.

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