Kreissparkasse Saalfeld-Rudolstadt Open Banking API

Reaching account data at Kreissparkasse Saalfeld-Rudolstadt no longer means wrestling with PSD2 certificates or a bespoke bank gateway. open-banking.io gives you one covered path to this Thuringian savings bank (BIC HELADEF1SAR), spanning both business and personal accounts, with every byte decrypted on your own device using a key only you hold.

The service is certificate-free and zero-knowledge: our servers keep only your public key, so they can move ciphertext but never read it. That means you get balances and transactions without handing a third party the ability to see them.

How to connect Kreissparkasse Saalfeld-Rudolstadt

Connecting happens entirely inside the open-banking.io dashboard — there is no API call, code, or key involved in linking the bank:

  1. Sign up for open-banking.io and set your encryption passphrase. Your keys are generated locally on your device at this step.
  2. In the dashboard, pick Kreissparkasse Saalfeld-Rudolstadt and choose the account type you need — business or personal.
  3. You are redirected to Kreissparkasse Saalfeld-Rudolstadt's own secure login, where you approve access on the bank's PSD2 consent screen.
  4. Your accounts sync back into your dashboard, ready to view. Consent lasts up to 180 days before the bank asks you to renew it.

Access your data

Once the connection exists, developers can optionally read it programmatically. On the Developers page, create an API key and export a credentials.json — this bundles the API key together with your private decryption key. From there the CLI (openbanking accounts, openbanking transactions, openbanking sync), an SDK, or the REST API all work. Requests authenticate with the X-Api-Key header, and every response is decrypted locally with your own key — an API key alone only ever returns ciphertext. Note the CLI and SDK only read and sync existing connections; there is no connect command.

All of this runs for roughly EUR 3/month across 2,600+ supported EU and UK banks.

Is a PSD2 certificate required?

No. open-banking.io is certificate-free — you approve access directly on Kreissparkasse Saalfeld-Rudolstadt's consent screen, and no eIDAS certificate is needed on your side.

Can open-banking.io see my Kreissparkasse Saalfeld-Rudolstadt transactions?

No. The platform is zero-knowledge and stores only your public key. Data is decrypted on your device with a private key that never leaves it.

Kreissparkasse Saalfeld-Rudolstadt permits a maximum consent window of 180 days, after which you re-approve access on the bank's login page.

Start at open-banking.io.