Sparkasse Südholstein API Access & Open Banking

Reaching your Sparkasse Südholstein accounts programmatically usually means wrestling with eIDAS certificates and bank-specific PSD2 sandboxes. open-banking.io removes that: it links to Sparkasse Südholstein (BIC NOLADE21SHO) on your behalf and streams both business and personal account data into one dashboard, while the decryption key that unlocks it never leaves your device.

The result is a certificate-free, zero-knowledge bridge to Sparkasse Südholstein. Our servers only ever hold your public key, so the balances and transactions we sync stay ciphertext until you decrypt them locally.

How to connect Sparkasse Südholstein

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 an encryption passphrase. Your key pair is generated right there on your own device.
  2. In the dashboard, search for and select Sparkasse Südholstein, then choose whether you're linking a business or personal account.
  3. You're redirected to Sparkasse Südholstein's own secure login, where you approve access under PSD2 — the standard bank consent screen.
  4. Once approved, your Sparkasse Südholstein accounts sync into the dashboard automatically. Consent lasts up to 180 days, after which you simply re-approve on the bank's screen.

Access your data

Want the data in code? That's an optional developer step you take after the account is linked. On the Developers page, create an API key and export a credentials.json — it 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 CLI and SDK only read and sync connections that already exist — they never create one. And an API key alone returns only ciphertext; without your private key there's nothing readable.

All of this runs at around EUR 3/month.

Do I need an eIDAS certificate for Sparkasse Südholstein?

No. open-banking.io handles the PSD2 layer, so you never touch certificates or QWAC setup.

Can open-banking.io read my Sparkasse Südholstein transactions?

No. It's zero-knowledge — we store only your public key, and decryption happens on your device.

Can I connect a Sparkasse Südholstein account from the CLI?

No. Connecting is done in the dashboard via the bank's consent screen; the CLI only reads and syncs existing links.

Start linking Sparkasse Südholstein at https://open-banking.io.