Sparkasse Gummersbach API Access & Open Banking

Reaching your Sparkasse Gummersbach accounts programmatically usually means certificates, sandboxes and paperwork. open-banking.io removes all of that. It links to Sparkasse Gummersbach (BIC WELADED1GMB) through regulated PSD2 access and lets you view and export both business and personal account data — balances and transactions — from one dashboard, with a single monthly subscription instead of a bank developer contract.

The difference is where your data lives. open-banking.io is zero-knowledge: the decryption key is generated on your own device and never leaves it, so the service only ever holds ciphertext and your public key. Nobody at open-banking.io can read your Sparkasse Gummersbach statements — only you can.

How to connect Sparkasse Gummersbach

Connecting happens entirely in 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 key pair is created locally at this moment.
  2. In the dashboard, search for Sparkasse Gummersbach and choose the account type you want to link — business or personal.
  3. You are redirected to Sparkasse Gummersbach's own secure login, where you authenticate and approve access on the bank's PSD2 consent screen.
  4. Once approved, your selected accounts sync back into the dashboard. Consent lasts up to 180 days, after which you simply re-approve on the bank's screen.

You never share your Sparkasse Gummersbach credentials with open-banking.io — they are only ever entered on the bank's site.

Access your data

Want the data in your own code? That's an optional developer step after the connection exists. On the Developers page, create an API key and download a credentials.json — it bundles the API key with your private decryption key. Then use the CLI (openbanking accounts, openbanking transactions, openbanking sync), an SDK, or the REST API. Requests carry the X-Api-Key header, and every response is decrypted locally with your key. The CLI and SDK only read and sync connections you already made in the dashboard — they cannot link a bank. An API key alone returns ciphertext; without your private key it stays unreadable.

All of this runs for roughly EUR 3/month, certificate-free.

Does open-banking.io store my Sparkasse Gummersbach login?

No. You authenticate directly on Sparkasse Gummersbach's site; open-banking.io never sees your credentials.

Yes — both types are supported. Add each from the dashboard and approve them separately.

How often do I re-authorise?

PSD2 consent runs up to 180 days per approval, then you re-confirm on the bank's screen.

Start at https://open-banking.io.