365.Bank open banking & API access via open-banking.io
Want to pull your 365.Bank balances and transactions into your own tools? open-banking.io gives you a single, privacy-first path to your Slovak account data — without chasing bank certificates or wrestling with raw PSD2 endpoints. 365.Bank covers both business and personal accounts, and a single approval keeps your data flowing for up to 180 days before you re-confirm. (365.Bank has no public BIC listed here, so there's nothing extra to look up.)
Everything runs on a zero-knowledge design: your encryption keys are generated on your own device, and open-banking.io only ever holds your public key. That means the service physically cannot read your statements — it stores ciphertext, and only you can turn it back into numbers.
How to connect 365.Bank
Connecting happens entirely in the open-banking.io dashboard — there's no code, no API call, and no key involved in this step.
- Sign up for open-banking.io and set your encryption passphrase. Your private key is created locally, on your machine, and never leaves it.
- In the dashboard, search for 365.Bank and choose the account type you want to link — business or personal.
- You're redirected to 365.Bank's own secure login, where you approve access on the bank's PSD2 consent screen. Your credentials go straight to the bank, never to open-banking.io.
- Once approved, your 365.Bank accounts sync into the dashboard, ready to view.
That's it — the consent is valid for 180 days, after which you simply re-approve.
Access your data
Developers get an optional programmatic layer after the account is connected. On the Developers page, create an API key and export a credentials.json — it 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 each response is decrypted locally with your own key. An API key on its own only ever returns ciphertext — without your private key, there's nothing readable to see. The CLI and SDK read and sync existing connections; they never create one.
FAQ
Does open-banking.io store my 365.Bank login?
No. You authenticate on 365.Bank's own consent screen, so your banking credentials are never shared with open-banking.io.
Can I connect 365.Bank with just an API key?
No. Linking always happens in the dashboard via the bank's consent flow. API keys only read data you've already connected.
How much does it cost?
Around EUR 3 per month for access to 2,600+ EU and UK banks, including 365.Bank.
Ready to start? Head to open-banking.io.