Sparekassen Kronjylland Open Banking & API Access
Reaching your Sparekassen Kronjylland account data used to mean eIDAS certificates, sandbox registrations and PSD2 paperwork. With open-banking.io none of that applies. This Danish savings bank connects through a single dashboard, and every balance and transaction that flows back is decrypted on your own device with a key that never leaves it. Whether you run a company account or a personal one, you get the same read access without touching a certificate authority.
How to connect Sparekassen Kronjylland
Connecting happens entirely inside the open-banking.io dashboard — there is no API call, code or key involved in this step.
- Sign up for open-banking.io and set your encryption passphrase. Your key pair is generated locally, so only you ever hold the private key.
- In the dashboard, choose Sparekassen Kronjylland and select the account type you need — business or personal are both supported.
- You are redirected to Sparekassen Kronjylland's own secure login, where you approve access under PSD2 consent. Because Sparekassen Kronjylland has no published BIC in our directory, you simply pick it by name.
- Your accounts sync straight into the dashboard. The consent lasts up to 180 days, after which you re-approve on the bank's screen.
Access your data
Once the connection exists, developers can optionally read it programmatically. 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. Every request carries the X-Api-Key header, and each response is decrypted locally with your own key. The API key alone only ever returns ciphertext; without your private key, nobody — including open-banking.io — can read it.
That is the essence of the zero-knowledge, certificate-free model: our servers hold only your public key. All of this runs for around EUR 3/month across 2,600+ supported banks.
Does open-banking.io store my Sparekassen Kronjylland login?
No. You authenticate directly on Sparekassen Kronjylland's own consent screen; we never see or store your credentials.
Can I connect a business account with the CLI?
No. Connecting always happens in the dashboard. The CLI and SDK only read and sync connections that already exist.
How long does access stay active?
Up to 180 days per consent, then you re-approve on Sparekassen Kronjylland's login screen.
Ready to start? Visit open-banking.io.