Sparkasse Zwickau API Access & Open Banking Data

Reading your Sparkasse Zwickau account data no longer means wrestling with bank certificates or PSD2 developer paperwork. open-banking.io gives you certificate-free, zero-knowledge access to your Sparkasse Zwickau balances and transactions — for both business and personal accounts (BIC WELADED1ZWI) — with a single consent that lasts up to 180 days. Your data is decrypted on your own device with a key only you hold; open-banking.io stores only your public key and never sees your unencrypted statements.

How to connect Sparkasse Zwickau

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 cryptographic keys are generated locally on your device, so the passphrase never leaves it.
  2. In the dashboard, search for Sparkasse Zwickau and choose the account type you need — business or personal.
  3. You are redirected to Sparkasse Zwickau's own secure login, where you approve access under PSD2. Your banking credentials go only to the bank.
  4. Once approved, your Sparkasse Zwickau accounts sync straight into your open-banking.io dashboard, ready to view.

The consent you grant on the bank's screen stays valid for up to 180 days before Sparkasse Zwickau asks you to re-authorise.

Access your data

Want to pull the data programmatically? That's an optional step you take after connecting. 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. Requests authenticate with the X-Api-Key header, and every response is decrypted locally with your own key. Without that private key, an API key alone returns only ciphertext — which is exactly how zero-knowledge should work. The CLI and SDK only read and sync connections you already made in the dashboard; there is no connect command.

All of this runs on a flat plan of roughly EUR 3 per month.

Do I need a developer account to use Sparkasse Zwickau?

No. Connecting and viewing accounts is a dashboard task. API keys and credentials.json are only for those who want programmatic access.

Can open-banking.io read my Sparkasse Zwickau transactions?

No. It holds only your public key. Everything is decrypted locally, so the service can never read your data.

Up to 180 days per approval. After that, you simply re-authorise on Sparkasse Zwickau's own consent screen.

Ready to start? Visit open-banking.io.