Edekabank API Access & Open Banking Integration

Edekabank (BIC EDEKDEHHXXX) is the banking arm of the EDEKA cooperative, and open-banking.io lets you reach its account data without wrestling with eIDAS certificates or PSD2 sandbox onboarding. Both business and personal accounts are supported, and every balance and transaction that flows in is decrypted on your own device with a key that never leaves it.

The idea is simple: open-banking.io acts as a certificate-free bridge to 2,600+ European banks. It stores only your public key, so its servers can move your ciphertext around but can never read a single figure inside it. That is what zero-knowledge means in practice.

How to connect Edekabank

Connecting happens entirely in the open-banking.io dashboard — there is no API call, code snippet, or developer key involved in this step.

  1. Sign up for an open-banking.io account.
  2. Set an encryption passphrase. Your encryption keys are generated locally on your device from this passphrase, so keep it safe.
  3. In the dashboard, pick Edekabank and choose the account type you need (business or personal).
  4. You are redirected to Edekabank's own secure login, where you approve access under PSD2. open-banking.io never sees your banking credentials.
  5. Your accounts sync back into the dashboard. A single consent stays valid for up to 180 days before Edekabank asks you to renew it.

Access your data

Once Edekabank is connected, reading the data programmatically is an optional developer step. From 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:

  • Use the CLI: openbanking accounts, openbanking transactions, openbanking sync.
  • Or call the REST API / SDK directly, passing your key in the X-Api-Key header.

Every response arrives encrypted and is decrypted locally with your private key. The CLI and SDK only read and sync connections that already exist — they never establish one. An API key on its own returns only ciphertext; without your private key the data stays unreadable.

All of this runs on the standard plan of roughly EUR 3/month.

Do I need an eIDAS certificate for Edekabank?

No. open-banking.io is certificate-free — you connect through the dashboard and approve access on Edekabank's own consent screen.

Can open-banking.io staff see my Edekabank transactions?

No. The service holds only your public key and stores encrypted data. Decryption happens on your device with a key only you control.

How often do I re-authorise?

Edekabank consent lasts up to 180 days. After that you simply re-approve from the dashboard to keep your accounts syncing.

Ready to start? Visit open-banking.io.