Skip to content
Banking/open banking

openbanking.org.uk:account-info-openapi

Account and Transaction API Specification sandbox and mock API

Swagger for Account and Transaction API Specification Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
29
Collections
-
Event types
-
Start this simulation
example request
curl https://your-openbanking-uk-account-info-openapi.slurry.io/accounts \
  -H "Authorization: Bearer slurry_sim_..."

Your simulation gets its own hostname, key and IP allow-list. Built from API version 3.1.7.

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 29.

  • POST/account-access-consents
  • GET/account-access-consents/{ConsentId}
  • DELETE/account-access-consents/{ConsentId}
  • GET/accounts
  • GET/accounts/{AccountId}
  • GET/accounts/{AccountId}/balances
  • GET/accounts/{AccountId}/beneficiaries
  • GET/accounts/{AccountId}/direct-debits
  • GET/accounts/{AccountId}/offers
  • GET/accounts/{AccountId}/parties
  • GET/accounts/{AccountId}/party
  • GET/accounts/{AccountId}/product