DiPocket API Access via Open Banking (Denmark)

Reaching your DiPocket (Denmark) balances and transactions from your own software is straightforward with open-banking.io. Rather than juggling PSD2 certificates or eIDAS registrations, you link DiPocket once through a hosted dashboard and everything you pull afterwards is decrypted on your own machine with a key nobody else holds. DiPocket (BIC DIUALT22) supports both business and personal accounts, and a single consent stays valid for up to 180 days before you re-approve.

How to connect DiPocket

Connecting happens entirely inside the open-banking.io web dashboard — there is no endpoint to call and no key to paste:

  1. Sign up for open-banking.io and set an encryption passphrase. Your keys are generated locally on your device, so the service only ever sees your public key.
  2. In the dashboard, search for DiPocket and choose the account type you hold (business or personal).
  3. You are redirected to DiPocket's own secure login, where you approve the access request (standard PSD2 consent).
  4. Once approved, your DiPocket accounts sync back into the dashboard and stay refreshed for the life of the consent.

That's the whole flow — a bank-hosted approval, not a developer handshake.

Access your data

Reading DiPocket programmatically is an optional step you take after the account is linked. On the Developers page, create an API key and export a credentials.json — it bundles the 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 directly. Every request carries the X-Api-Key header, and each response is decrypted locally with your key. An API key on its own only ever returns ciphertext, which is exactly the point of a zero-knowledge design.

At roughly EUR 3/month, the service stays certificate-free and keeps your DiPocket data readable only to you.

FAQ

Do I connect DiPocket with an API key?

No. Linking is done in the dashboard, where DiPocket's own login screen handles approval. API keys only come into play later, for reading data you've already connected.

Can open-banking.io read my DiPocket transactions?

No. Its servers hold only your public key, so stored data is encrypted. Decryption happens on your device using the private key in your credentials.json.

Up to 180 days. After that you simply re-approve DiPocket through the dashboard to keep the sync alive.

Ready to start? Visit open-banking.io.