DiPocket API Access & Open Banking Integration
Need programmatic reach into your DiPocket accounts? open-banking.io links DiPocket to a single, privacy-first workspace where balances and transactions land ready to read. DiPocket serves both business and personal customers (BIC DIUALT22), and a granted consent stays valid for up to 180 days before you renew it — so you set things up once and let the data flow.
The service is certificate-free and zero-knowledge: your encryption keys are generated on your own device, and open-banking.io only ever holds your public key. It covers 2,600+ EU and UK banks for roughly EUR 3/month, DiPocket included.
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.
- Sign up and choose an encryption passphrase. Your private decryption key is created locally, in your browser, and never leaves your device.
- In the dashboard, search for DiPocket and select the account type you hold — business or personal.
- You're redirected to DiPocket's own secure login, where you approve access under PSD2. Your credentials are entered only on DiPocket's site.
- Once approved, your DiPocket accounts sync straight into your dashboard, refreshed automatically for the life of the 180-day consent.
Access your data
Want the data in your own scripts? That's an optional step you take after the connection above is live. On 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. Every request carries your key in the X-Api-Key header, and each response is decrypted locally with the private key only you hold. These tools read and sync connections you've already made — they never establish a new one. And because the servers store only ciphertext, an API key on its own returns unreadable data without your key.
Does open-banking.io ever see my DiPocket login?
No. You authenticate on DiPocket's own consent screen; open-banking.io never receives your banking credentials.
Can open-banking.io read my transactions?
No. It holds only your public key. Data is decrypted on your device with a private key that never leaves it.
How long does a DiPocket connection last?
Up to 180 days per consent. When it lapses, a quick re-approval on DiPocket's screen restores the sync.
Ready to start? Connect DiPocket at open-banking.io.