apoBank API Access & Open Banking Integration

Deutsche Apotheker- und Ärztebank (apoBank, BIC DAAEDEDD) is the German cooperative bank for healthcare professionals. With open-banking.io you can pull your apoBank account and transaction data into a single dashboard — and, if you want, read it programmatically — without certificates, without eIDAS QWACs, and without handing anyone a key to your data.

open-banking.io is a zero-knowledge open-banking service covering 2,600+ EU and UK banks. Your data is encrypted with a key generated on your own device and decrypted locally, so our servers only ever hold your public key. apoBank supports both personal and business accounts, with a maximum consent lifetime of 180 days before you re-authorise.

How to connect apoBank

Connecting happens entirely in 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 set your encryption passphrase. Your keys are generated locally on your device; the passphrase never leaves it.
  2. In the dashboard, choose apoBank and select the account type you hold (personal or business).
  3. You are redirected to apoBank's own secure login, where you approve access under PSD2 — your credentials go only to apoBank.
  4. Once consent is granted, your accounts sync back into your open-banking.io dashboard, and refresh automatically for up to 180 days.

That's the whole flow: pick the bank, approve on apoBank's screen, watch your accounts appear.

Access your data

Reading your data programmatically is an optional developer step you take after connecting. On 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 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. An API key on its own only returns ciphertext — without your private key, nobody (including us) can read it. Note that the CLI and SDK only read and sync connections you have already made in the dashboard; there is no connect command.

All of this runs from around EUR 3/month.

Does open-banking.io ever see my apoBank data unencrypted?

No. Encryption and decryption happen on your device. Our servers store only your public key and encrypted blobs.

Can I connect apoBank with an API key?

No — connecting is done in the dashboard by approving access on apoBank's login. API keys are only for reading data afterwards.

How long does apoBank access last?

Up to 180 days per consent, after which you re-approve on apoBank's screen.

Ready to start? Visit open-banking.io.