Wartburg-Sparkasse API Access & Open Banking Data

Reaching your Wartburg-Sparkasse account data no longer means wrestling with bank APIs or PSD2 certificates. open-banking.io gives you a single, certificate-free path to your Eisenach-based Sparkasse (BIC HELADEF1WAK), covering both business and personal accounts. You approve access once, and your balances and transactions flow into a dashboard that only you can decrypt — the service holds your public key and nothing more.

Because everything is zero-knowledge, open-banking.io never sees your statements in the clear. Your encryption keys are generated on your own device from a passphrase you choose, so decrypted Wartburg-Sparkasse data exists only where you control it.

How to connect Wartburg-Sparkasse

Connecting happens entirely inside the open-banking.io dashboard — there is no API call, code, or key involved in linking the account:

  1. Sign up for open-banking.io and open the web dashboard.
  2. Set your encryption passphrase. This generates your personal key pair locally; keep the passphrase safe, as it is what unlocks your data.
  3. Pick Wartburg-Sparkasse in the dashboard and choose the account type — business or personal.
  4. Approve on Wartburg-Sparkasse's own login. You are redirected to the bank's secure consent screen to authorise access under PSD2. Consent can last up to 180 days before you renew it.
  5. Accounts sync. Once approved, your Wartburg-Sparkasse accounts and transactions appear in your dashboard, decrypted locally.

Access your data

Programmatic access is an optional step after the account is already connected. From the Developers page, create an API key and export a credentials.json that bundles the API key together with your private decryption key. Then read your data with the CLI (openbanking accounts, openbanking transactions, openbanking sync), an SDK, or the REST API. Every request sends the X-Api-Key header, and every response is decrypted locally with your own key — the API key alone only ever returns ciphertext. The CLI and SDK read and sync existing connections; they never create one.

At roughly EUR 3/month, you get ongoing access without per-certificate fees or enterprise onboarding.

FAQ

Does open-banking.io use an API key to connect my bank?

No. Linking Wartburg-Sparkasse is done in the dashboard by approving on the bank's own consent screen. API keys only come into play later, for optional programmatic reads.

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

No. It is zero-knowledge and stores only your public key. Data is decrypted on your device with a key only you hold.

Wartburg-Sparkasse grants up to 180 days per approval, after which you re-confirm access from your dashboard.

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