DiPocket API Access & Open Banking Integration

Want a single, private way to reach your DiPocket account data? open-banking.io links to DiPocket (Spain) using regulated PSD2 access, then keeps everything under a key that never leaves your device. DiPocket covers business and personal accounts, carries the BIC DIUALT22, and grants a consent window of up to 180 days before you re-approve.

Unlike traditional aggregators, open-banking.io is zero-knowledge and certificate-free. You don't chase an eIDAS certificate or hand a third party a readable copy of your finances. Our servers only ever hold your public key, so what lands on them is ciphertext — the plain values appear only after your own device decrypts them.

How to connect DiPocket

Connecting happens entirely in 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 open the web dashboard.
  2. Set an encryption passphrase. Your encryption keys are generated locally, on your machine, from this passphrase.
  3. In the dashboard, choose DiPocket and pick the account type — business or personal.
  4. You're redirected to DiPocket's own secure login, where you approve access on their consent screen (standard PSD2 authorisation).
  5. Once approved, your DiPocket accounts and transactions sync straight into your dashboard.

That's the whole flow. You never share DiPocket credentials with us — you authenticate on DiPocket's side, and the consent stays valid for the 180-day maximum.

Access your data

Reading DiPocket data programmatically is an optional developer step that comes after the connection above exists. From the Developers page, create an API key and export a credentials.json. That file bundles two things: the API key and your private decryption key.

With it you can run the CLI — openbanking accounts, openbanking transactions, openbanking sync — or call the SDK or REST API. Requests authenticate with the X-Api-Key header, and every response is decrypted locally with your private key. The API key alone only ever returns ciphertext; without your key there is nothing readable to leak.

All of this runs for around EUR 3/month, with 2,600+ EU/UK banks supported.

FAQ

Do I need a developer setup to use DiPocket?

No. Connecting and viewing DiPocket accounts is done in the dashboard. The API key and CLI are optional, for programmatic reads only.

Can open-banking.io read my DiPocket balances?

No. It's zero-knowledge — we store only your public key, so data stays encrypted until your device decrypts it.

How long does DiPocket access last?

Up to 180 days per consent, after which you re-approve on DiPocket's login.

Ready to begin? Start at open-banking.io.