DiPocket API Access & Open Banking Data | open-banking.io

Reaching your DiPocket account data no longer means wrestling with PSD2 certificates or bank-specific integrations. open-banking.io gives you one certificate-free path to your DiPocket balances and transactions across France and the wider EU/UK — covering 2,600+ banks in total — while keeping the data encrypted so that only you can read it.

DiPocket (BIC DIUALT22) works with open-banking.io for both business and personal accounts, and a single approval keeps your access live 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 code, endpoint or API key involved in this step.

  1. Sign up for open-banking.io and set your encryption passphrase. Your keys are generated locally on your own device, so the service never sees them.
  2. In the dashboard, choose DiPocket from the bank list and pick the account type you want to link — business or personal.
  3. You are redirected to DiPocket's own secure login, where you approve access under PSD2 consent. Your credentials stay with DiPocket.
  4. Once approved, your DiPocket accounts sync straight into your dashboard, ready to view and refresh.

Access your data

Want to work with the data programmatically? That's an optional step you take after the connection above already exists. Open the Developers page, create an API key, and export a credentials.json — this bundles your 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 CLI and SDK only read and sync connections you've already approved in the dashboard — they never establish new ones.

Because open-banking.io is zero-knowledge, its servers hold only your public key. An API key on its own returns ciphertext; without your private key, nobody — not even open-banking.io — can turn it into readable account data. All of this runs on a flat ~EUR 3/month plan.

FAQ

Do I need an eIDAS certificate to reach DiPocket?

No. open-banking.io is certificate-free. You approve access on DiPocket's own consent screen and never handle PSD2 certificates yourself.

Can the CLI connect my DiPocket account for me?

No. Connecting is a dashboard-only action. The CLI, SDK and REST API read and sync accounts you have already linked — there is no connect command.

Up to 180 days per approval. When it expires, you re-approve on DiPocket's login to keep syncing.

Ready to start? Visit open-banking.io.