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

Tokuda Bank (BIC CREXBGSF) is a Sofia-based commercial bank serving Bulgarian retail and corporate customers. With open-banking.io you can pull your Tokuda Bank balances and transaction history into one place under PSD2, without wrestling with certificates, eIDAS onboarding or a sandbox. The service covers 2,600+ EU and UK banks, and everything you sync is decrypted locally with a key only you hold — a genuinely zero-knowledge, certificate-free setup.

Both personal and business Tokuda Bank accounts are supported, and each authorisation you grant stays valid for up to 180 days before the bank asks you to renew it.

How to connect Tokuda Bank

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 open the dashboard.
  2. Set your encryption passphrase. Your key pair is generated on your own device, so the private key never leaves it.
  3. Pick Tokuda Bank from the bank list and choose the account type — business or personal.
  4. You are redirected to Tokuda Bank's own secure login, where you approve access on the bank's PSD2 consent screen.
  5. Once approved, your accounts sync back into your dashboard and refresh automatically.

Because approval takes place on Tokuda Bank's own login, your banking credentials are only ever seen by the bank itself.

Access your data

Reading Tokuda Bank data programmatically is an optional step after the connection 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), an SDK, or the REST API directly. Requests carry the X-Api-Key header, and every response is decrypted locally on your machine. An API key alone only ever returns ciphertext; without your private key, nothing is readable — the open-banking.io servers hold only your public key and can never see your data. The CLI and SDK read and sync existing connections; they don't create new ones.

FAQ

Do I need a developer account or certificate to connect Tokuda Bank?

No. Connecting is done in the dashboard by approving access on Tokuda Bank's consent screen. Certificates and API keys are never required to link a bank.

Up to 180 days. After that, Tokuda Bank prompts you to re-authorise, which you do again from the dashboard.

What does it cost?

Around EUR 3 per month, covering Tokuda Bank and every other supported bank on your account.

Ready to start? Visit open-banking.io.