DiPocket API Access & Open Banking Connection

Reach your DiPocket balances and transactions through open-banking.io, a certificate-free EU/UK open-banking service covering 2,600+ banks. You link DiPocket once in the dashboard, and every figure that lands on your screen is decrypted on your own device with a key nobody else holds.

DiPocket serves business and personal accounts (BIC DIUALT22), and a single approval grants a read consent valid for up to 180 days before you renew it.

How to connect DiPocket

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 key pair is generated locally, so only your public key ever reaches the servers.
  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 PSD2 consent on the bank's screen. open-banking.io never sees your banking credentials.
  4. Your DiPocket accounts sync back into the dashboard, ready to view and refresh.

That is the whole flow: pick the bank, approve at the source, and your data appears.

Access your data

Once DiPocket is connected, developers can optionally read the same data programmatically. On the Developers page, create an API key and export a credentials.json file — it bundles your API key together with your private decryption key.

From there, use the CLI:

openbanking accounts
openbanking transactions
openbanking sync

…or call the REST API / SDK directly. Every request carries your key in the X-Api-Key header, and each response is decrypted locally with your private key. The API key alone only returns ciphertext — without the private key living on your machine, the payload stays unreadable. There is no connect command; the tooling reads and syncs the connection you already approved in the dashboard.

This is what zero-knowledge means in practice: open-banking.io stores encrypted blobs and your public key, nothing more. All of it runs at roughly EUR 3/month, with no eIDAS certificate or bank-sponsored onboarding required.

FAQ

Do I need an API key to connect DiPocket?

No. Connecting is done in the dashboard by approving consent on DiPocket's login page. API keys are only for reading data afterward.

Up to 180 days per approval, after which you re-authorise from the dashboard.

Can open-banking.io read my DiPocket transactions?

No. Data is decrypted only on your device with your private key; the servers hold ciphertext and your public key.

Start at open-banking.io.