Urbo API Access & Open Banking Integration Guide

Urbo bankas serves personal and business customers across Lithuania, and open-banking.io lets you reach that account data without wrestling with eIDAS certificates or a PSD2 sandbox. Urbo (BIC MDBALT22XXX) supports both business and personal account types, and a single approved consent stays valid for up to 180 days before you need to renew it. Everything runs through one encrypted workspace that only you can unlock.

How to connect Urbo

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 keys are generated locally on your own device, so nobody else can derive them.
  2. In the dashboard, choose Urbo and select the account type you hold (business or personal).
  3. You are redirected to Urbo's own secure login, where you approve access on the bank's official PSD2 consent screen.
  4. Once approved, your Urbo accounts and transactions sync back into your dashboard automatically.

Because approval takes place on Urbo's own systems, your banking credentials are never seen by open-banking.io.

Access your data

Programmatic access is an optional step you can take after the connection exists. 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 you can use the CLI (openbanking accounts, openbanking transactions, openbanking sync), an SDK, or the REST API directly. Requests authenticate with the X-Api-Key header, and each response is decrypted locally with your own key. The CLI and SDK only read and sync existing connections — they never create one.

This is what makes the service zero-knowledge: open-banking.io stores only your public key, so its servers hold ciphertext they cannot read. It is also certificate-free and covers 2,600+ EU and UK banks for around EUR 3/month.

Does an API key alone return readable Urbo data?

No. An API key on its own only returns encrypted data. Readable output requires your private decryption key from credentials.json, applied locally.

Up to 180 days. After that window you simply reauthorize Urbo through the dashboard to keep data flowing.

Can I connect Urbo from the CLI?

No. Connecting is done only in the dashboard via Urbo's consent screen. The CLI, SDK, and API read or sync connections that already exist.

Start at open-banking.io.