Kasseler Sparkasse Open Banking & API Access

Kasseler Sparkasse (BIC HELADEF1KAS) serves personal and business customers across the Kassel region of Hesse. With open-banking.io you can bring both account types into one secure workspace and, if you build software, read balances and transactions programmatically — all without certificates, bank contracts or PSD2 licences of your own.

open-banking.io connects to 2,600+ EU and UK banks. What makes it different is the trust model: it is zero-knowledge. Your encryption keys are generated on your own device from a passphrase you choose, so the service only ever holds your public key. It can relay ciphertext but can never read your Kasseler Sparkasse data.

How to connect Kasseler Sparkasse

Connecting happens entirely inside 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 private decryption key is created locally and never leaves your device.
  2. In the dashboard, choose Kasseler Sparkasse and select the account type you need — business or personal.
  3. You are redirected to Kasseler Sparkasse's own secure login, where you approve access under PSD2. Consent lasts up to 180 days before you renew it.
  4. Your approved accounts sync back into the dashboard, ready to view.

Because you authorise everything on the bank's genuine consent screen, your credentials are never seen by open-banking.io.

Access your data

Once Kasseler Sparkasse is connected, developers can optionally read the data in code. Open the Developers page, create an API key, and export a credentials.json bundling that key with your private decryption key. Then use the CLI (openbanking accounts, openbanking transactions, openbanking sync), an SDK, or the REST API. Requests authenticate with the X-Api-Key header, and every response is decrypted locally with your own key — an API key alone only ever returns ciphertext. Note that the CLI and SDK only read and sync existing connections; there is no connect command.

All of this costs around EUR 3 per month.

Do I need a developer agreement with Kasseler Sparkasse?

No. open-banking.io provides the regulated PSD2 access. You just approve consent on the bank's login screen.

Can open-banking.io see my Kasseler Sparkasse transactions?

No. It is zero-knowledge and holds only your public key. Data is decrypted on your device with a key only you have.

How long does access stay active?

Kasseler Sparkasse permits consent for up to 180 days, after which you re-approve to keep syncing.

Ready to start? Visit open-banking.io.