Qonto Italy API Access & Open Banking Data
Qonto has become a go-to account for Italian founders, freelancers and finance teams — but pulling your own transaction history out of it for bookkeeping, dashboards or reconciliation is another story. open-banking.io gives you a single, standards-based way to reach your Qonto data (BIC QNTOITM2XXX) without wrestling with eIDAS certificates or bank-specific developer portals. It covers both business and personal account types, and every consent lasts up to 180 days before you simply re-approve.
The difference here is where your data lives. open-banking.io is zero-knowledge: the encryption keys are generated on your own device, and our servers only ever hold your public key. Whatever syncs down from Qonto is decrypted locally, by you — never in our infrastructure.
How to connect Qonto
Connecting happens entirely inside the open-banking.io dashboard — there is no API call, key or code involved in this step.
- Sign up for open-banking.io and set your encryption passphrase. This generates your personal key pair locally, on your device.
- In the dashboard, search for Qonto and choose your account type (business or personal).
- You're redirected to Qonto's own secure login, where you approve access under PSD2 consent — your credentials go straight to Qonto, never to us.
- Once approved, your accounts and transactions sync back into your dashboard, ready to browse.
That's the whole flow. No developer redirect, no OAuth wiring on your side.
Access your data
Want to work with the data programmatically? That's an optional step you take after connecting. 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. Requests authenticate with the X-Api-Key header, and every response is decrypted locally with your own key. An API key on its own only ever returns ciphertext — without your private key, the data stays unreadable.
At around EUR 3/month, it's a low-cost, certificate-free route into your Qonto accounts.
Is my Qonto login shared with open-banking.io?
No. You authenticate on Qonto's own consent screen; we never see your banking credentials.
Can open-banking.io read my transactions?
No. It's zero-knowledge — we hold only your public key, and decryption happens on your device.
How long does a Qonto connection stay active?
Up to 180 days per PSD2 consent, after which you re-approve in the dashboard.
Start at open-banking.io.