Sparkasse Essen API Access & Open Banking Integration

Reaching your Sparkasse Essen account data no longer means wrestling with eIDAS certificates or a PSD2 sandbox. open-banking.io gives you a single, certificate-free path to your Essen accounts — whether you hold a personal current account or run a business relationship with the bank. Sparkasse Essen sits behind BIC SPESDE3EXXX, and both business and personal account types are supported. Consent can last up to 180 days before you re-approve, matching the maximum the bank permits under PSD2.

The design is deliberately zero-knowledge: your encryption keys are generated on your own device, and open-banking.io only ever holds your public key. Nobody on the server side — not even the service itself — can read your Sparkasse Essen balances or transactions.

How to connect Sparkasse Essen

Connecting happens entirely in the open-banking.io dashboard, not through any API call or key.

  1. Sign up for open-banking.io and set an encryption passphrase. Your private key is derived locally and never leaves your machine.
  2. In the dashboard, search for Sparkasse Essen and choose the account type you want to link — business or personal.
  3. You are redirected to Sparkasse Essen's own secure login, where you approve access using your normal banking credentials (the standard PSD2 consent screen).
  4. Once approved, your accounts and transactions sync back into your dashboard, encrypted with your key.

There is no code to write for this step, and no developer ever redirects you — you authorise directly on the bank's site.

Access your data

Want to work with the data programmatically? That's an optional step after connecting. On the Developers page, create an API key and export a credentials.json — it 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. Requests carry 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 it stays unreadable. Note the CLI and SDKs only read and sync connections you already made in the dashboard; there is no connect command.

All of this runs for around EUR 3/month.

Do I need an eIDAS certificate for Sparkasse Essen?

No. open-banking.io is certificate-free — you authenticate directly on Sparkasse Essen's consent screen, nothing else required.

Can open-banking.io see my Sparkasse Essen transactions?

No. It's zero-knowledge and holds only your public key. Decryption happens on your device with a key only you have.

Sparkasse Essen allows up to 180 days per approval, after which you re-authorise in the dashboard.

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