iBanFirst API Access & Open Banking Integration

Reaching your iBanFirst accounts programmatically usually means chasing PSD2 certificates and bank-specific sandboxes. open-banking.io removes that overhead: it links iBanFirst (BIC FXBBBEBBXXX) to a single, unified layer, then hands you the tools to read the data on your own terms. Both business and personal accounts are supported, and each consent stays valid for up to 180 days before you renew it.

The design is deliberately zero-knowledge. Your encryption keys are generated on your own device from a passphrase you set, and open-banking.io stores only your public key. Account data is decrypted locally, so the service never sees it in the clear — and there are no eIDAS certificates to buy or manage.

How to connect iBanFirst

Connecting happens entirely inside the open-banking.io dashboard — there is no API call, code, or key at this stage:

1. Sign up and set your encryption passphrase; your keys are created on your device.
2. In the dashboard, choose iBanFirst and select the account type (business or personal).
3. You are redirected to iBanFirst's own secure login to approve access under PSD2.
4. Once you confirm the consent, your iBanFirst accounts sync into the dashboard.

That approval screen belongs to iBanFirst, not to us — your credentials are never entered anywhere else.

Access your data

Once the connection is live, developers can optionally read it in code. Open 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 directly. Calls authenticate with the X-Api-Key header, and every response is decrypted locally with your key. An API key on its own only ever returns ciphertext, so nothing readable leaves your machine.

All of this runs for roughly EUR 3/month, with no per-call or certificate fees.

FAQ

Do I connect iBanFirst using an API key?

No. Connecting is done in the dashboard, where you approve access on iBanFirst's own login screen. API keys come later and only read data you have already connected.

Can the CLI or SDK link my account?

No — they read and sync existing connections only. There is no connect command; linking always goes through the dashboard consent flow.

Can open-banking.io read my iBanFirst data?

No. It holds only your public key. Everything is decrypted locally with the private key you alone control.

Start at open-banking.io.