Oberbank API Access & Open Banking Integration

Reaching your Oberbank balances and transaction history no longer means wrestling with bank-issued certificates or a PSD2 developer sandbox. With open-banking.io you link your Oberbank account once and then view — or programmatically read — the data through a single, privacy-first service that spans 2,600+ EU and UK banks.

Oberbank (BIC OBKLDEMXXXX) is supported for both business and personal account types, and a single approval keeps the connection live for up to the regulatory maximum of 180 days before you re-confirm.

How to connect Oberbank

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

  1. Sign up at open-banking.io and set your encryption passphrase. Your keys are generated locally on your own device, so nobody else can decrypt what flows through.
  2. Open the dashboard, search for Oberbank, and choose whether you are linking a business or personal account.
  3. You are redirected to Oberbank's own secure login, where you approve access on the bank's PSD2 consent screen — your credentials are only ever entered with Oberbank.
  4. Once approved, your accounts and transactions sync straight into your open-banking.io dashboard, ready to view.

Access your data

After the connection exists, developers can optionally read it in code. 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 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. The CLI and SDK only read and sync connections you already made in the dashboard — they never establish a new one.

Because open-banking.io is zero-knowledge, its servers hold only your public key. An API key on its own returns ciphertext; without your private key it stays unreadable — even to us. No eIDAS certificate is required, and access costs roughly EUR 3 per month.

Does connecting Oberbank need a certificate?

No. There are no certificates or QWACs to obtain. You approve access directly on Oberbank's consent page and the link is active immediately.

Oberbank supports both types. Link each account through the dashboard; each carries its own consent lasting up to 180 days.

Can open-banking.io read my Oberbank transactions?

No. Data is decrypted only on your device with a key you alone hold, so the service itself cannot read your account information.

Ready to begin? Start at open-banking.io.