openbankingproject.ch
Swiss NextGen Banking API-Framework sandbox and mock API
# Summary The **Swiss NextGen API** is based on the NextGenPSD2 *Framework Version 1.3.4* of the Berlin Group which offers a modern, open, harmonised and interoperable set of Application Programming Interfaces (APIs) as the safest and most efficient way to provide data securely. The NextGen Framework reduces XS2A complexity and costs, addresses the problem of multiple competing standards in Europe Writes persist, data moves on a schedule and every change can fire a signed webhook.
- Operations
- 34
- Collections
- -
- Event types
- -
curl https://your-openbankingproject-ch.slurry.io/v1/accounts \
-H "Authorization: Bearer slurry_sim_..."Your simulation gets its own hostname, key and IP allow-list. Built from API version 1.3.8_2020-12-14 - Swiss edition 1.3.8.1-CH.
What gets simulated
Collections, relationships and state machines are worked out from the spec when you start the simulation.
- State. Creates, updates and deletes persist and show up in later reads.
- Behaviour. Records move through their states on a schedule you control, and you can fast-forward up to 30 days.
- Webhooks. Every change emits a signed, retried event.
- Failure. Per-endpoint errors, latency and chaos rules, on demand.
Operations
First 12 of 34.
- GET/v1/accounts
- GET/v1/accounts/{account-id}
- GET/v1/accounts/{account-id}/balances
- GET/v1/accounts/{account-id}/transactions
- GET/v1/accounts/{account-id}/transactions/{transactionId}
- POST/v1/consents
- GET/v1/consents/{consentId}
- DELETE/v1/consents/{consentId}
- GET/v1/consents/{consentId}/authorisations
- POST/v1/consents/{consentId}/authorisations
- GET/v1/consents/{consentId}/authorisations/{authorisationId}
- PUT/v1/consents/{consentId}/authorisations/{authorisationId}