Sparkasse Wittenberg API Access & Open Banking

Reaching your Sparkasse Wittenberg accounts programmatically usually means chasing PSD2 certificates and per-bank paperwork. open-banking.io removes that overhead: it gives you a single, secure way to view and export your Sparkasse Wittenberg data across more than 2,600 EU and UK banks — no eIDAS certificate, no bank-by-bank onboarding. Your account information is decrypted on your own device with a key that never leaves it, so the service itself only ever sees ciphertext.

Sparkasse Wittenberg (BIC NOLADE21WBL) is supported for both business and personal accounts, with a maximum consent lifetime of 180 days before you simply re-approve.

How to connect Sparkasse Wittenberg

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 cryptographic keys are generated locally, on your device, at this moment.
  2. In the dashboard, search for and select Sparkasse Wittenberg, then choose whether you're linking a business or personal account.
  3. You're redirected to Sparkasse Wittenberg's own secure login, where you approve access under PSD2 — your credentials are entered only on the bank's site, never with us.
  4. Once approved, your accounts and transactions sync straight into your dashboard, and the consent stays valid for up to 180 days.

Access your data

After a connection exists, developers can optionally read it programmatically. On the Developers page, create an API key and export a credentials.json — this bundles your 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 directly. Every request carries the X-Api-Key header, and each response is decrypted locally with your own key. The API key alone only returns ciphertext — without your private key, no one, including our servers, can read it. Note that the CLI and SDK only read and sync connections that already exist; they never create one.

All of this runs for around EUR 3/month.

Is open-banking.io zero-knowledge?

Yes. Our servers hold only your public key. Decryption happens on your device, so we can never read your Sparkasse Wittenberg data.

Do I need a PSD2 certificate?

No. open-banking.io is certificate-free — you approve access directly on Sparkasse Wittenberg's consent screen.

How long does access last?

Up to 180 days per consent. When it expires, you re-approve in the dashboard in a few clicks.

Ready to start? Visit open-banking.io.