Kreissparkasse Heinsberg API Access & Open Banking

Pulling account and transaction data out of Kreissparkasse Heinsberg (BIC WELADED1ERK) usually means wrestling with PSD2 certificates and a sandbox onboarding. open-banking.io removes that friction: it maintains the regulated connection to Kreissparkasse Heinsberg for you, so you get a clean feed of your own account data without registering as a licensed provider or holding an eIDAS certificate. Both business and personal accounts are supported, and a single consent lasts up to 180 days before you renew it.

Everything is built around a zero-knowledge model. When you sign up you set an encryption passphrase, and the keys derived from it never leave your device. open-banking.io stores only your public key, so the ciphertext on its servers is meaningless without the private key that stays with you.

How to connect Kreissparkasse Heinsberg

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

  1. Create your open-banking.io account and set an encryption passphrase. Your key pair is generated locally on your own device.
  2. In the dashboard, pick Kreissparkasse Heinsberg from the bank list and choose the account type you want to link — business or personal.
  3. You are redirected to Kreissparkasse Heinsberg's own secure login, where you approve access on the bank's PSD2 consent screen.
  4. Once approved, your accounts sync back into the dashboard. That consent stays valid for up to 180 days.

Access your data

Reading the data programmatically is an optional step for developers, and only after the connection above exists. 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 use the CLI (openbanking accounts, openbanking transactions, openbanking sync), an SDK, or the REST API. Every request carries your X-Api-Key header, and each response is decrypted locally with your own key — the API key alone only ever returns ciphertext. The CLI and SDK read and sync existing connections; they never create one.

All of this runs on the standard plan at roughly EUR 3 per month.

Do I need an eIDAS or PSD2 certificate?

No. open-banking.io holds the regulated access, so you connect Kreissparkasse Heinsberg and read data without any certificate of your own.

Can open-banking.io read my Kreissparkasse Heinsberg data?

No. It is zero-knowledge and stores only your public key. Data is decrypted on your device with a private key that never leaves it.

Kreissparkasse Heinsberg permits a maximum consent window of 180 days, after which you re-approve access from the dashboard.

Ready to start? Visit open-banking.io.