Caisse d'Epargne Bourgogne Franche-Comté API access

Bringing your Caisse d'Epargne Bourgogne Franche-Comté accounts into your own tooling shouldn't mean chasing an eIDAS certificate or standing up a PSD2 sandbox. open-banking.io gives you a single, private path to your balances and transactions across 2,600+ EU and UK banks — including this regional caisse of the Caisse d'Epargne (BPCE) network. Both business and personal accounts are supported, and a single approval keeps data flowing for up to 180 days before you renew.

The defining trait is privacy. open-banking.io is zero-knowledge and certificate-free: your encryption keys are generated on your own device, and the service only ever holds your public key. Every balance and transaction that lands in your dashboard is decrypted locally, so nobody — not even open-banking.io's servers — can read your Caisse d'Epargne Bourgogne Franche-Comté data.

How to connect Caisse d'Epargne Bourgogne Franche-Comté

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

  1. Sign up and set an encryption passphrase. Your private key is derived on your device and never leaves it.
  2. In the dashboard, search for Caisse d'Epargne Bourgogne Franche-Comté and choose the account type — business or personal.
  3. You're redirected to Caisse d'Epargne Bourgogne Franche-Comté's own secure login, where you approve access on the bank's PSD2 consent screen.
  4. Once approved, your accounts sync back into the dashboard automatically, refreshing within the 180-day consent window.

Because approval happens on the bank's side, your credentials are only ever entered on Caisse d'Epargne Bourgogne Franche-Comté's pages. (Note: no public BIC is listed for this caisse; the connection relies on the bank name, not a BIC.)

Access your data

Reading the data programmatically is an optional developer step you take after the bank is connected. Open the Developers page, create an API key, and export a credentials.json that bundles the API key with your private decryption key. From there:

  • CLI: openbanking accounts, openbanking transactions, openbanking sync
  • Any SDK or the REST API, authenticating with the X-Api-Key header

Every response is decrypted locally with your key. An API key on its own only ever returns ciphertext — the readable data appears solely on your machine.

Does open-banking.io connect the bank via an API?

No. Connecting is done in the dashboard, where you approve access on Caisse d'Epargne Bourgogne Franche-Comté's own login. The CLI and SDK only read or sync connections that already exist.

What does it cost?

Around EUR 3 per month for access across all supported banks.

Can open-banking.io read my transactions?

No. It stores only your public key; decryption happens on your device.

Start at open-banking.io.