Berenberg API Access & Open Banking Integration

Berenberg, one of Germany's oldest private banks (BIC BEGODEHHXXX), holds account data that's yours to reach — statements, balances, and transaction history. open-banking.io gives you a single, privacy-first route to that data without certificates, eIDAS registration, or a bank-by-bank integration project. Both business and personal Berenberg accounts are supported, with PSD2 consent lasting up to 180 days before you re-approve.

Unlike traditional aggregators, open-banking.io is zero-knowledge. Encryption keys are generated on your own device from a passphrase only you know, and the service stores only your public key. Every response is decrypted locally, so open-banking.io's servers never see your Berenberg data in readable form.

How to connect Berenberg

Connecting happens entirely in the open-banking.io dashboard — there's 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 created locally, on your device.
  2. In the dashboard, search for and select Berenberg, then choose the account type (business or personal).
  3. You're redirected to Berenberg's own secure login, where you authenticate and approve access on the bank's PSD2 consent screen.
  4. Once approved, your Berenberg accounts sync into your dashboard automatically and stay current for the life of the 180-day consent.

That's the whole flow — no developer redirect, no manual credential handling.

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 — this bundles your API key together with your private decryption key. From there:

  • Use the CLI: openbanking accounts, openbanking transactions, openbanking sync
  • Or an SDK, or the REST API directly

Requests authenticate with the X-Api-Key header, and each response is decrypted locally with your private key. Note the two-part security model: an API key alone only ever returns ciphertext — without your private key, the data stays unreadable. There's no connect command; the tools read and sync connections you've already made in the dashboard.

All of this runs at around EUR 3/month.

Do I need an eIDAS certificate for Berenberg?

No. open-banking.io is certificate-free — you approve access on Berenberg's login and skip the regulatory tooling entirely.

Can open-banking.io read my Berenberg data?

No. It's zero-knowledge and holds only your public key. Data is decrypted on your device with a key only you hold.

How long does access to Berenberg last?

Up to 180 days per consent. After that, simply re-approve on Berenberg's consent screen to keep your data syncing.

Start at open-banking.io.