Sparkasse Gunzenhausen API Access & Open Banking

Pulling your Sparkasse Gunzenhausen account data into a spreadsheet, a dashboard, or your own code usually means wrestling with bank portals and certificates. open-banking.io removes that friction: it links to Sparkasse Gunzenhausen (BIC BYLADEM1GUN) under PSD2 and streams your business and personal account data into one place — encrypted so that only you can read it. There are no eIDAS certificates to obtain and nothing to install to get started.

The service is zero-knowledge by design. When you sign up you set an encryption passphrase, and the keys behind it are generated on your own device. open-banking.io keeps only your public key, so its servers can move your Sparkasse Gunzenhausen data around but never decrypt it. All of this runs for roughly EUR 3 per month.

How to connect Sparkasse Gunzenhausen

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

  1. Create your open-banking.io account and set your encryption passphrase; your private key is created locally and never leaves your device.
  2. In the dashboard, search for Sparkasse Gunzenhausen and choose the account type you need — business or personal.
  3. You are redirected to Sparkasse Gunzenhausen'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. Consent lasts up to 180 days, after which you simply re-approve on the bank's screen.

Access your data

Reading the data programmatically is an optional step you take after the connection exists. On the Developers page, create an API key and export a credentials.json — it bundles that API key together with your private decryption key. From there the CLI (openbanking accounts, openbanking transactions, openbanking sync), the SDKs, and the REST API all work the same way: requests carry your key in the X-Api-Key header, and every response is decrypted locally with your private key. The API key alone only ever returns ciphertext — without your key there is nothing readable to see. The CLI and SDKs read and sync existing connections; they never establish one.

Can I connect Sparkasse Gunzenhausen with just an API key?

No. Connecting is done in the dashboard by approving access on Sparkasse Gunzenhausen's consent page. API keys only read data you have already linked.

Can open-banking.io staff see my transactions?

No. The platform holds only your public key, so your Sparkasse Gunzenhausen data is decrypted solely on your own device.

Which accounts are supported?

Both business and personal Sparkasse Gunzenhausen accounts, with consent valid for up to 180 days per approval.

Start at https://open-banking.io.