Forbrugsforeningen API Access & Open Banking

Forbrugsforeningen is a Danish membership association that gives its members a payment and benefits account, and under PSD2 you have the right to reach that account data through a licensed third party. open-banking.io makes that practical: it links your Forbrugsforeningen account into a single dashboard and, crucially, keeps the data readable only by you. Every balance and transaction is decrypted on your own device with a key that never leaves it — the service holds nothing but your public key.

Forbrugsforeningen supports both business and personal account types, and a single consent stays valid for up to 180 days before you renew it. No eIDAS certificate, no QWAC, and no bank sandbox paperwork are required on your side — open-banking.io carries the regulated plumbing.

How to connect Forbrugsforeningen

Connecting happens entirely inside 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 encryption keys are generated locally on your device at this moment.
2. In the dashboard, choose Forbrugsforeningen from the bank list and pick the account type you need (business or personal).
3. You are redirected to Forbrugsforeningen's own secure login, where you approve access on the bank's PSD2 consent screen.
4. Once approved, your accounts sync back into the dashboard and refresh automatically until the 180-day consent expires.

Because approval happens on Forbrugsforeningen's own page, your credentials are never seen by open-banking.io.

Access your data

Reading the data programmatically is an optional developer step you take after the connection above exists. Open the Developers page, create an API key, and export a credentials.json — it bundles that 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. Requests authenticate with the X-Api-Key header, and every response is decrypted locally with your own key. The API key alone only ever returns ciphertext; without your private key the payload stays unreadable — that is what zero-knowledge means in practice. Note Forbrugsforeningen publishes no BIC, so identify the account within your dashboard rather than by SWIFT code.

All of this runs on the standard ~EUR 3/month plan, with no per-connection or per-call surcharge.

Does open-banking.io ever see my Forbrugsforeningen data?

No. The servers store only your public key. Data is decrypted on your device, so nobody at open-banking.io can read your balances or transactions.

Do I need a certificate to connect Forbrugsforeningen?

No. The service is certificate-free — no eIDAS or QWAC is needed from you. open-banking.io holds the PSD2 licensing.

Can the CLI connect my Forbrugsforeningen account?

No. The CLI and SDK only read and sync connections that already exist. Connecting is done once in the dashboard on Forbrugsforeningen's consent screen.

Start at open-banking.io.