Pleo API Access & Open Banking (Norway) | open-banking.io

Pleo is a spend-management platform, and its Norwegian accounts carry real transaction data — card spend, wallet balances and settlements — that you may want to pull into your own tools. open-banking.io gives you a single, PSD2-compliant path to that data without wrangling certificates, eIDAS registrations or a bespoke bank integration. You link Pleo once in the dashboard, and everything after that is either automatic sync or an optional developer export that you control.

The defining trait here is privacy. open-banking.io is zero-knowledge and certificate-free: your encryption keys are generated on your own device, and the platform only ever holds your public key. That means Pleo balances and transactions are decrypted locally, by you — the servers can store ciphertext but can never read it.

How to connect Pleo

Connecting happens entirely in the open-banking.io dashboard — there is no API call, code snippet or key involved in this step.

  1. Sign up for open-banking.io and set an encryption passphrase. Your private key is derived on your device and never leaves it.
  2. In the dashboard, search for Pleo (Norway) and choose your account type — business or personal are both supported.
  3. You are redirected to Pleo's own secure login to approve access under PSD2. You grant consent directly on the bank's screen; open-banking.io never sees your credentials.
  4. Once approved, your Pleo accounts sync into the dashboard. The consent stays valid for up to 180 days, after which you simply re-approve.

Pleo's BIC for reference is PLEODKK2.

Access your data

Reading Pleo data programmatically is an optional step for developers, taken only after the connection above exists. On the Developers page, create an API key and export a credentials.json — this bundles the API key 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 authenticates with the X-Api-Key header, and each response is decrypted locally with your own key. An API key alone only returns ciphertext — without your private key, the data stays unreadable. Note that the CLI and SDK read and sync existing connections; they never create one.

Pricing is roughly EUR 3/month, covering access to 2,600+ EU/UK banks.

Do I need eIDAS certificates to reach Pleo?

No. open-banking.io is certificate-free — you connect through the dashboard and approve access on Pleo's own login screen.

Can open-banking.io read my Pleo transactions?

No. It is zero-knowledge and holds only your public key. All decryption happens on your device with a key only you have.

Can I connect Pleo from the CLI?

No. Connecting is done in the dashboard. The CLI, SDK and REST API only read or sync connections that already exist.

Ready to start? Visit open-banking.io.