Unicaja Banco API Access & Open Banking Data

Reaching your Unicaja Banco accounts through a single, privacy-first interface is what open-banking.io is built for. Whether you keep a personal current account or run a business relationship with the Málaga-based lender, open-banking.io lets you view balances and transactions in one dashboard — and, if you write code, pull the same data programmatically. Unicaja Banco (BIC UCJAES2MXXX) is one of 2,600+ EU and UK institutions supported, and access is granted under PSD2 with a consent window of up to 180 days before you re-approve.

The defining trait here is zero knowledge. open-banking.io never holds a certificate on your behalf and never sees your data in the clear. Your encryption keys are generated on your own device from a passphrase only you know, so everything that syncs is decrypted locally — the service stores only your public key.

How to connect Unicaja Banco

Connecting happens entirely in 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 private key is created locally at this moment and never leaves your device.
  2. In the dashboard, search for Unicaja Banco and choose the account type you hold — business or personal.
  3. You are redirected to Unicaja Banco's own secure login, where you authenticate and approve the PSD2 consent directly with the bank.
  4. Once you confirm, your accounts sync back into the dashboard and stay current for the life of the consent.

At no point does open-banking.io ask for your banking credentials — you enter them only on Unicaja Banco's site.

Access your data

Once a connection exists, developers can read it programmatically — an optional extra step. On the Developers page, create an API key and export a credentials.json, which bundles that key with your private decryption key. Then use the CLI (openbanking accounts, openbanking transactions, openbanking sync), an SDK, or the REST API. Requests authenticate with the X-Api-Key header, and every response is decrypted locally with your key. The API key alone returns only ciphertext — readable data requires the private key held on your machine. Note the CLI reads and syncs existing connections; it cannot create one.

All of this runs at roughly EUR 3/month.

Does open-banking.io store my Unicaja Banco password?

No. You authenticate only on Unicaja Banco's own login screen; open-banking.io never receives your credentials.

Can open-banking.io staff read my transactions?

No. The service is zero-knowledge and holds only your public key, so your data stays encrypted server-side.

How long does access last before I re-approve?

Up to 180 days, after which Unicaja Banco asks you to renew consent.

Start at open-banking.io.