Sparkasse Ulm API Access & Open Banking Integration

Reaching your Sparkasse Ulm account data no longer means wrestling with eIDAS certificates or a bespoke bank integration. open-banking.io gives you PSD2-compliant access to Sparkasse Ulm (BIC SOLADES1ULM) through a single dashboard that covers 2,600+ European banks. Whether you hold a business or personal account, you authorise once and your balances and transactions flow into a place only you can decrypt.

The service is zero-knowledge: your encryption keys are generated on your own device, and open-banking.io only ever stores your public key. Nobody on the server side — not even the platform — can read your Sparkasse Ulm statements. And because it is certificate-free, there is nothing to procure, renew, or install.

How to connect Sparkasse Ulm

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

  1. Sign up for an open-banking.io account.
  2. Set an encryption passphrase. This generates your personal key pair locally, so decryption stays on your machine.
  3. In the dashboard, pick Sparkasse Ulm and choose the account type (business or personal).
  4. You are redirected to Sparkasse Ulm's own secure login, where you approve access on the bank's official PSD2 consent screen.
  5. Your accounts sync back into the dashboard, ready to view.

Consent lasts up to 180 days, after which you simply re-approve on Sparkasse Ulm's screen to keep the connection live.

Access your data

Once Sparkasse Ulm is connected, developers can optionally read the data programmatically. From the Developers page, create an API key and export a credentials.json — which 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. An API key alone only ever returns ciphertext; without your private key, the data stays unreadable. Note the CLI and SDK only read and sync existing connections — there is no connect command.

All of this runs for roughly EUR 3/month.

Do I need an eIDAS certificate for Sparkasse Ulm?

No. open-banking.io is certificate-free — you authorise directly on the bank's consent screen.

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

No. The platform holds only your public key; decryption happens on your device.

How long does access last?

Up to 180 days per consent, then you re-approve with Sparkasse Ulm.

Start at open-banking.io.