bunq Estonia API Access & Open Banking Connection

Reading your bunq (Estonia) accounts programmatically usually means wrestling with certificates, sandbox registrations, and PSD2 paperwork. open-banking.io removes all of that. It gives you certificate-free access to bunq across the EU and UK, alongside 2,600+ other banks, and it stays zero-knowledge: your data is decrypted on your own device with a key nobody else — not even open-banking.io — can hold.

bunq supports both personal and business accounts, so whether you run the app for everyday spending or company finances, the same connection covers it. There is no BIC to look up here, and each authorisation you grant lasts up to 180 days before bunq asks you to renew it.

How to connect bunq

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

1. Sign up for an open-banking.io account.
2. Set your encryption passphrase. Your keys are generated locally on your device at this moment, so only you can later unlock your data.
3. In the dashboard, pick bunq from the bank list and choose the account type you need — personal or business.
4. You are redirected to bunq's own secure login, where you approve access on their consent screen (standard PSD2 authorisation).
5. Your accounts flow back into the dashboard and begin syncing.

That is the whole flow. You never hand your bunq credentials to open-banking.io — approval happens on bunq's side.

Access your data

Once bunq is connected, reading the data programmatically is an optional developer step. Open the Developers page, create an API key, and export a credentials.json file. That file bundles the API key together with your private decryption key — the key that turns ciphertext back into readable figures.

From there you can use the CLI (openbanking accounts, openbanking transactions, openbanking sync), an SDK, or the REST API directly. Requests carry your key in the X-Api-Key header, and every response is decrypted locally with your private key. Without that key, the API returns only ciphertext — which is exactly why the service can be zero-knowledge while still being fully programmable.

All of this runs for around EUR 3 per month.

Do I need certificates or a bunq developer account?

No. open-banking.io is certificate-free. You connect bunq through its normal consent screen — no eIDAS certificate or sandbox registration required.

Can open-banking.io read my bunq transactions?

No. The service stores only your public key. Your data is decrypted locally with a private key that never leaves your device.

How long does access last?

Each bunq authorisation is valid for up to 180 days. After that you re-approve on bunq's consent screen to keep syncing.

Ready to start? Visit open-banking.io.