Skip to content
Banking/open banking

docs.yapily.com

Yapily sandbox and mock API

The Yapily API enables connections between your application and users' banks. For more information check out our [documentation](/introduction). In particular, make sure to view our [Getting Started](/getting-started/get-started) steps if this is your first time here. While testing the API, our list of [sandbox credentials](/resources/sandbox/sandbox-credentials) maybe useful. Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
96
Collections
-
Event types
-
Start this simulation Vendor documentation
example request
curl https://your-yapily.slurry.io/accounts \
  -H "Authorization: Bearer slurry_sim_..."

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

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

  • POST/account-auth-requests
  • PUT/account-auth-requests
  • PATCH/account-auth-requests
  • GET/accounts
  • GET/accounts/{accountId}
  • GET/accounts/{accountId}/balances
  • GET/accounts/{accountId}/beneficiaries
  • GET/accounts/{accountId}/direct-debits
  • GET/accounts/{accountId}/periodic-payments
  • GET/accounts/{accountId}/scheduled-payments
  • GET/accounts/{accountId}/statements
  • GET/accounts/{accountId}/statements/{statementId}