levoBank open banking API access — read your data
Reaching your levoBank accounts no longer means wrestling with bank APIs, eIDAS certificates, or a sandbox onboarding queue. open-banking.io is a certificate-free bridge to more than 2,600 EU and UK banks — levoBank (BIC GENODE51LEB) among them — and it works for both business and personal accounts. You approve access once, and your balances and transactions flow into a single dashboard that only you can decrypt.
The design is zero-knowledge from end to end. When you sign up you set an encryption passphrase, and the keys are generated on your own device. open-banking.io stores only your public key, so its servers can never read or decrypt what they relay — the plaintext exists only where you hold the private key.
How to connect levoBank
Connecting happens entirely inside the open-banking.io dashboard — there is no API call, code, or key involved in this step.
- Sign up for open-banking.io and set your encryption passphrase (your keys are generated locally).
- In the dashboard, pick levoBank and choose the account type you need — business or personal.
- You are redirected to levoBank's own secure login, where you approve access under PSD2 consent.
- Your accounts sync back into the dashboard, ready to view.
Consent lasts up to 180 days, after which you simply re-approve on levoBank's screen to keep the connection live.
Access your data
Once levoBank is connected, reading the data programmatically is an optional developer step. 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 you can use the CLI (openbanking accounts, openbanking transactions, openbanking sync), an SDK, or the REST API directly.
Every request carries the X-Api-Key header, and every response is decrypted locally with your own key. The API key alone only ever returns ciphertext — without your private key, the data stays unreadable. There is no connect command: the CLI and SDK read and sync existing connections, never establish new ones.
All of this runs for roughly EUR 3/month.
FAQ
Do I need a developer account to connect levoBank?
No. Connecting is done in the dashboard by approving access on levoBank's login. API keys are only for reading data afterward.
Can open-banking.io see my levoBank transactions?
No. It holds only your public key. Data is decrypted on your device, so the service never sees your plaintext.
How long does my levoBank consent last?
Up to 180 days per PSD2 rules. Re-approve on levoBank's consent screen to renew.
Ready to start? Visit open-banking.io.