Sparkasse Bochum API Access & Open Banking Data

Pulling your Sparkasse Bochum (BIC WELADED1BOC) account data into your own tools usually means wrestling with bank certificates and PSD2 paperwork. open-banking.io removes that friction: it is a certificate-free bridge to 2,600+ EU and UK banks, including Sparkasse Bochum, and it works for both business and personal accounts. You approve access once, your balances and transactions sync into a dashboard, and — because everything is decrypted on your own device — the service never holds a readable copy of your data.

How to connect Sparkasse Bochum

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 an open-banking.io account.
  2. Set an encryption passphrase. Your key pair is generated locally on your device — open-banking.io only ever sees your public key.
  3. In the dashboard, search for Sparkasse Bochum and choose the account type you hold: business or personal.
  4. You are redirected to Sparkasse Bochum's own secure login, where you approve access on the bank's PSD2 consent screen.
  5. Your accounts sync back into the dashboard, ready to view.

The consent Sparkasse Bochum grants lasts up to 180 days, after which you simply re-approve on the bank's screen to keep the connection live.

Access your data

Once a connection exists, reading it programmatically is an optional developer step. Open 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 you can 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 private key. That is the crux of the zero-knowledge design: an API key alone returns only ciphertext from open-banking.io's servers — without the private key held on your device, the data stays unreadable. The CLI and SDK read and sync existing connections; they never create one.

All of this runs for around EUR 3 per month.

Does open-banking.io store my banking credentials?

No. You authenticate on Sparkasse Bochum's own login page, and open-banking.io holds only your public key — it cannot decrypt what it stores.

Can I connect Sparkasse Bochum with the CLI?

No. Connecting is done in the dashboard via the bank's consent screen. The CLI only reads and syncs connections you have already approved.

How long does access last?

Sparkasse Bochum permits a maximum consent window of 180 days. When it expires, re-approve on the bank's screen to continue syncing.

Start at open-banking.io.