Saxo Bank Open Banking & Secure API Data Access
Saxo Bank is a Danish investment and banking specialist, and its account data falls under PSD2 — meaning you have the right to share it with tools you choose. open-banking.io gives you that access without certificates, eIDAS setup, or a screen-scraping middleman. It links to Saxo Bank (BIC SAXODKKKXXX) across 2,600+ European institutions, covering both business and personal accounts, with consent valid for up to 180 days before a quick renewal.
What sets it apart is the trust model. open-banking.io is zero-knowledge: your encryption keys are generated on your own device, and the service only ever holds your public key. Balances and transactions are sealed before they leave, so nobody on the server side can read them — the data is decrypted locally, on your machine, with a key only you hold.
How to connect Saxo Bank
Connecting happens entirely in 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 created right there on your device, never uploaded.
- In the dashboard, search for Saxo Bank and choose the account type you want to link — business or personal.
- You're redirected to Saxo Bank's own secure login to approve access. You authenticate and grant PSD2 consent directly with the bank, so your credentials never touch open-banking.io.
- Once approved, your Saxo Bank accounts sync into your dashboard, ready to view and refresh.
That consent covers a 180-day window, after which you simply re-approve on Saxo Bank's screen.
Access your data
Want your Saxo Bank data in code? 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 with your private decryption key. From there, use the CLI (openbanking accounts, openbanking transactions, openbanking sync), an SDK, or the REST API. Every request carries the X-Api-Key header, and each response is decrypted locally with your own key. An API key alone only ever returns ciphertext — without your private key it stays unreadable, which is the whole point.
All of this runs for around EUR 3/month.
Is my Saxo Bank login shared with open-banking.io?
No. You authenticate on Saxo Bank's own consent page; open-banking.io never sees your banking credentials.
Can I connect Saxo Bank from the CLI?
No — connecting is dashboard-only. The CLI, SDK, and API only read and sync connections you've already approved.
Does open-banking.io need an eIDAS certificate?
No. It's certificate-free, so there's nothing for you to obtain or renew.
Start at open-banking.io.