Bethmann Bank API Access: Sync Accounts via Open Banking
Pulling account data out of Bethmann Bank no longer means wrestling with eIDAS certificates or bespoke bank integrations. With open-banking.io you point a single REST endpoint at Bethmann Bank (BIC DELBDE33XXX) and start syncing live financial data into your own product, ledger or reporting stack. The private-banking arm serves both business and personal relationships, and both account types are reachable through the same interface.
How to connect Bethmann Bank
- Create an open-banking.io account and generate an API key.
- Call the institutions endpoint and select Bethmann Bank (Germany).
- Send your customer to the hosted consent screen to authenticate directly with the bank.
- Receive the returned consent token and begin requesting data.
- Refresh on your own schedule until the consent window closes.
What data you can access
Once a customer approves the link, the API exposes their accounts (IBANs, currency, product metadata), real-time balances including available and booked figures, and dated transaction history with counterparties and remittance details. Everything arrives as clean, normalised JSON, so a Bethmann Bank account looks identical in your code to any of the other institutions you connect.
Consent and coverage
A single authorisation stays valid for up to 180 days before the customer needs to re-approve, giving you long-lived read access without constant re-prompts. Bethmann Bank is one node in a network of 2,600+ banks across the EU and UK, so the same integration scales the moment you add a second institution.
Privacy by design
The platform is zero-knowledge: credentials are entered only on the bank's own domain, and we never store or relay them. There are no QWAC or QSEAL certificates to buy, renew or install — the compliance and PSD2 plumbing sits entirely on our side, so your team ships instead of provisioning.
Pricing
Access starts at roughly EUR 3 per month, a flat, predictable rate rather than per-call metering or enterprise contracts.
Is a certificate required to use the Bethmann Bank API?
No. The service is certificate-free — no eIDAS QWAC/QSEAL setup is needed on your end.
How long does Bethmann Bank consent last?
Up to 180 days per authorisation, after which the customer simply reconfirms access.
Can I read both business and personal accounts?
Yes. Both account types Bethmann Bank offers are supported through the same endpoints.
Ready to build? Start at open-banking.io.