Sparkasse Göttingen API Access & Open Banking

Pulling account and transaction data out of Sparkasse Göttingen (BIC NOLADE21GOE) usually means wrestling with certificates, sandbox registrations and bank-specific PSD2 portals. open-banking.io removes all of that. It is a single, certificate-free service covering 2,600+ banks across the EU and UK, and it connects to Sparkasse Göttingen through the same regulated PSD2 rails your banking app uses — no developer onboarding with the Sparkasse required. Both business and personal accounts are supported, and a single consent stays valid for up to 180 days before you renew it.

What makes the service different is the trust model. open-banking.io is zero-knowledge: your encryption keys are generated on your own device, and the platform only ever holds your public key. Every piece of Sparkasse Göttingen data you retrieve is decrypted locally, so nobody — not open-banking.io, not a third party — can read your balances or transactions server-side.

How to connect Sparkasse Göttingen

Connecting happens entirely inside 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. This generates your personal key pair locally; only you hold the private key.
  2. In the dashboard, choose Sparkasse Göttingen from the bank list and select the account type you want — business or personal.
  3. You are redirected to Sparkasse Göttingen's own secure login and consent screen, where you approve access directly with the bank (standard PSD2 authorisation).
  4. Your accounts sync back into the dashboard, and you can view balances and transactions right away.

That is the whole flow. Consent runs for the maximum 180-day window, after which you re-approve on the bank's screen.

Access your data

Once Sparkasse Göttingen is connected, reading the data programmatically is an optional developer step. From the Developers page, create an API key and export a credentials.json — this bundles your API key together with your private decryption key. Then use the CLI (openbanking accounts, openbanking transactions, openbanking sync), an SDK, or the REST API. Requests authenticate with the X-Api-Key header, and each response is decrypted locally with your key. An API key alone only ever returns ciphertext — without your private key, the data stays unreadable. The CLI and SDK read and sync existing connections; they never connect a bank.

All of this runs on the same ~EUR 3/month subscription.

Do I need a certificate or PSD2 licence?

No. open-banking.io is certificate-free, and you authorise access directly on Sparkasse Göttingen's consent screen.

Can open-banking.io see my Sparkasse Göttingen data?

No. The service is zero-knowledge and holds only your public key; decryption happens on your device.

How long does access last?

Up to 180 days per consent, then you simply re-approve with the bank.

Start at open-banking.io.