Erzgebirgssparkasse API Access & Open Banking Data

Erzgebirgssparkasse serves the Ore Mountains region of Saxony, and open-banking.io lets you reach its account and transaction data without EIDAS certificates, screen-scraping scripts, or a bank-side developer programme. Whether you run a business or personal account, you link it once through a regulated PSD2 flow and then read balances and payment history on your own terms. Because open-banking.io is zero-knowledge, everything is decrypted on your device with a key only you hold — the service stores only your public key and never sees your figures in the clear.

How to connect Erzgebirgssparkasse

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 generated locally, on your own device.
  2. In the dashboard, search for Erzgebirgssparkasse (BIC WELADED1STB) and choose your account type — both business and personal accounts are supported.
  3. You are redirected to Erzgebirgssparkasse's own secure login, where you approve access on the bank's PSD2 consent screen.
  4. Your accounts sync back into the dashboard. Consent lasts up to 180 days, after which you simply re-approve on the bank's screen.

Access your data

Once the connection is live, developers can optionally read it programmatically. On 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. Requests authenticate with the X-Api-Key header, and every response is decrypted locally with your own key. The API key alone only ever returns ciphertext, so even a leaked key exposes nothing readable. Note that the CLI and SDK only read and sync connections you already made in the dashboard — there is no connect command.

All of this runs at around EUR 3/month, with no certificate paperwork.

Do I need a developer account with Erzgebirgssparkasse?

No. You approve access directly on Erzgebirgssparkasse's login screen; open-banking.io handles the PSD2 plumbing.

Can open-banking.io read my Erzgebirgssparkasse balances?

No. Data is encrypted with your key and decrypted only on your device. The servers hold your public key alone.

How long does access last?

Erzgebirgssparkasse grants consent for up to 180 days. When it expires, re-approve on the bank's own screen to keep syncing.

Ready to start? Visit open-banking.io.