Berliner Sparkasse API Access & Open Banking Data

Berliner Sparkasse is one of the largest municipal savings banks in Germany, serving households and companies across the capital. If you want a clean, programmatic view of your Berliner Sparkasse money — balances, statements, transaction history — open-banking.io gives you PSD2 access without certificates, without eIDAS hoops, and without ever handing your raw data to a third party. Everything is decrypted on your own device with a key that only you hold.

open-banking.io reaches 2,600+ banks across the EU and UK, and Berliner Sparkasse (BIC BELADEBEXXX) is fully supported for both business and personal accounts, with consent lasting up to 180 days before you re-approve.

How to connect Berliner Sparkasse

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 open your dashboard.
  2. Set an encryption passphrase. Your encryption keys are generated locally on your device, so open-banking.io never sees them.
  3. Pick Berliner Sparkasse in the dashboard and choose the account type — business or personal.
  4. Approve on Berliner Sparkasse's own login. You are redirected to the bank's secure consent screen, where you authenticate directly with Berliner Sparkasse and grant access.
  5. Your accounts sync back into the dashboard, ready to view.

That's it — the account holder is always the one approving access, on the bank's own screen.

Access your data

Reading Berliner Sparkasse data programmatically is an optional step for developers, available after you've connected. 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. Every request carries the X-Api-Key header, and every response is decrypted locally with your own key. The API key alone only ever returns ciphertext — without your private key, nobody (including open-banking.io) can read it.

This is what zero-knowledge means in practice: open-banking.io holds only your public key. All of this runs for roughly EUR 3/month.

FAQ

Do I need an eIDAS certificate to access Berliner Sparkasse?

No. open-banking.io is certificate-free. You approve access on Berliner Sparkasse's own consent screen — no QWAC or QSeal certificate required.

Can I connect a Berliner Sparkasse business account?

Yes. Both business and personal accounts are supported. Choose the account type in the dashboard when you pick the bank.

Berliner Sparkasse permits consent for up to 180 days. After that you simply re-approve on the bank's login screen.

Ready to start? Visit open-banking.io.