Sparkasse Slovenia: Open Banking & API Access

Reaching your Sparkasse (Slovenia) account data no longer means wrestling with eIDAS certificates or a bespoke bank integration. open-banking.io gives you a single, certificate-free path to your Slovenian Sparkasse balances and transactions across both business and personal accounts, under a PSD2 consent that stays valid for up to 180 days before you renew it.

The service is zero-knowledge by design. When you sign up you set an encryption passphrase, and the keys derived from it are generated on your own device. open-banking.io only ever holds your public key, so the account data flowing back from Sparkasse is decrypted locally — the platform itself can never read it.

How to connect Sparkasse

Connecting happens entirely inside the open-banking.io dashboard, not through any code or API call:

  1. Create an open-banking.io account and set your encryption passphrase (your private key is generated locally and never leaves your device).
  2. In the dashboard, search for Sparkasse (Slovenia) and choose the account type you need — business or personal.
  3. You're redirected to Sparkasse's own secure login, where you authenticate and approve access on the bank's PSD2 consent screen.
  4. Once approved, your Sparkasse accounts sync back into your dashboard, ready to view.

No developer credentials, redirect URIs, or keys are involved in this step — approval is granted directly by you, on Sparkasse's own pages. Note that a BIC is not currently published for this integration; selecting the bank by name in the dashboard is all you need.

Access your data

Programmatic access is an optional step you can take after a connection exists. On the Developers page, generate an API key and export a credentials.json — this bundles your 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 authenticates with the X-Api-Key header, and each response is decrypted locally with your own key. There is no connect command — the CLI and SDK only read and sync connections you already approved in the dashboard. An API key on its own returns nothing but ciphertext; without your private key, the data stays sealed.

All of this runs for around EUR 3/month.

FAQ

Do I need an eIDAS certificate for Sparkasse?

No. open-banking.io is certificate-free — you authorise access by logging in on Sparkasse's own consent screen.

Can open-banking.io read my Sparkasse data?

No. The platform holds only your public key; your transactions are decrypted on your device with a key only you control.

Up to 180 days, after which you re-approve access through Sparkasse to keep syncing.

Start connecting your Sparkasse accounts at open-banking.io.