Sparkasse Aachen API Access & Open Banking Data

Pulling your Sparkasse Aachen balances and transactions into your own tools usually means wrestling with eIDAS certificates and a PSD2 sandbox. open-banking.io removes that entirely: it is a certificate-free bridge to 2,600+ EU and UK banks, and everything you sync from Sparkasse Aachen (BIC AACSDE33XXX) is decrypted locally with a key that never leaves your device. You get standardised access to both business and personal accounts without registering as a licensed provider.

Because the platform is zero-knowledge, its servers only ever hold your public key. Encrypted account data flows through, but nobody at open-banking.io — or anyone who breaches it — can read your Sparkasse Aachen statements. Only you hold the private key that turns ciphertext back into numbers.

How to connect Sparkasse Aachen

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 an encryption passphrase. Your key pair is generated right there on your own device.
  2. In the dashboard, search for Sparkasse Aachen and choose the account type you want to link — business or personal.
  3. You are redirected to Sparkasse Aachen's own secure login, where you approve access under PSD2. Your credentials go only to the bank.
  4. Once approved, your selected 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 Sparkasse Aachen data programmatically is an optional step you take after the account is connected. Open the Developers page, create an API key, and export a credentials.json — this file bundles the 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 directly. Requests authenticate with the X-Api-Key header, and every response is decrypted locally on your machine. The API key alone only ever returns ciphertext — without your private key, the data stays unreadable. Note there is no connect command: the CLI and SDK read and refresh existing links, never create them.

All of this runs on a flat plan of roughly EUR 3/month.

Does open-banking.io store my Sparkasse Aachen login?

No. You authenticate directly on Sparkasse Aachen's login screen; the platform never sees your banking password.

Which Sparkasse Aachen accounts are supported?

Both business and personal accounts can be linked and synced.

How long does access last before I re-approve?

PSD2 consent runs for up to 180 days, then you re-confirm on the bank's own consent screen.

Start syncing Sparkasse Aachen data at https://open-banking.io.