Caisse d'Epargne Midi-Pyrénées Open Banking API

Reading your own Caisse d'Epargne Midi-Pyrénées data shouldn't require an eIDAS certificate, a regulator sandbox, or a banking-grade compliance stack. open-banking.io gives individuals and developers a single, private doorway to their accounts at this BPCE-group Occitanie bank (BIC CEPAFRPP313), covering both business and personal relationships under a 180-day consent window.

Everything is built around a zero-knowledge design. Your encryption keys are generated on your own device, and open-banking.io's servers only ever hold your public key — so balances and transactions are decrypted locally, never on our infrastructure. It's certificate-free, works across 2,600+ EU and UK banks, and costs roughly EUR 3/month.

How to connect Caisse d'Epargne Midi-Pyrénées

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 keys are created right there on your device.
  2. In the dashboard, choose Caisse d'Epargne Midi-Pyrénées and select the account type you want to link — business or personal.
  3. You're redirected to Caisse d'Epargne Midi-Pyrénées's own secure login, where you approve access on the bank's PSD2 consent screen.
  4. Once approved, your accounts sync into your dashboard, and the consent stays valid for up to 180 days before you re-authorise.

Because approval takes place on the bank's own page, your credentials are never seen or stored by open-banking.io.

Access your data

After a connection exists, developers can optionally read it programmatically. Open the Developers page, create an API key, and export a credentials.json — this bundles your 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.

Every request authenticates with 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 is nothing readable to leak. The CLI and SDK read and sync existing connections; they never create one.

Is a certificate or developer account required?

No. open-banking.io is certificate-free. You just need an open-banking.io account and your Caisse d'Epargne Midi-Pyrénées online banking credentials for the consent step.

Can open-banking.io read my transactions?

No. It's zero-knowledge — servers hold only your public key, so your data is decrypted only on your device.

Does this cover business accounts?

Yes. Both business and personal Caisse d'Epargne Midi-Pyrénées accounts are supported, each with a 180-day consent.

Ready to start? Visit open-banking.io.