DiPocket API Access & Open Banking Integration

Want programmatic reach into your DiPocket (Bulgaria) accounts without wrestling with eIDAS certificates or a bespoke bank integration? open-banking.io gives you a single, privacy-first path to your DiPocket balances and transactions. DiPocket carries the BIC DIUALT22, supports both business and personal account types, and grants consent windows of up to 180 days before you re-authorise.

The defining trait here is zero-knowledge design. Your encryption keys are generated on your own device from a passphrase you choose, and every figure that leaves DiPocket is decrypted locally. open-banking.io servers only ever hold your public key, so they store ciphertext they cannot read. No qualified certificates, no bank-specific paperwork — and it covers 2,600+ EU and UK banks for roughly EUR 3/month.

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 private key is derived on your device and never uploaded.
  2. In the dashboard, choose DiPocket and select the account type you hold (business or personal).
  3. You are redirected to DiPocket's own secure login, where you approve access under PSD2 — the standard bank consent screen.
  4. Once you confirm, your DiPocket accounts sync straight into your open-banking.io dashboard.

That consent stays valid for up to 180 days, after which you simply repeat the approval to keep the data flowing.

Access your data

Reading DiPocket data programmatically is an optional developer step that comes after the connection above exists. 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.
  • Or call the SDK / REST API directly, sending your key in the X-Api-Key header.

The CLI, SDK and API only read or refresh connections you already made in the dashboard — none of them can connect a bank. Every response is decrypted locally with your private key, so an API key on its own returns nothing but ciphertext.

FAQ

Does open-banking.io need an eIDAS certificate for DiPocket?

No. It is certificate-free — you authorise access on DiPocket's own login screen, nothing more.

Can open-banking.io staff see my DiPocket transactions?

No. The service is zero-knowledge and holds only your public key; decryption happens on your device.

Is a business DiPocket account supported?

Yes. Both business and personal DiPocket accounts work, with consent lasting up to 180 days.

Start at open-banking.io.