Skip to content
Banking/open banking

bigredcloud.com

Big Red Cloud sandbox and mock API

<div style='line-height: 30px;'> <strong>Welcome to the Big Red Cloud API</strong><br/> This API enables programmatic access to Big Red Cloud data.<br/> We have used Swagger to auto generate the API documentation on this page, and it also enables direct interaction with the API in this page. <br/> To get started, you will require an API Key - check out our guide at <a target='_blank' href='https: Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
111
Collections
-
Event types
-
example request
curl https://your-bigredcloud.slurry.io/api/v1/accounts \
  -H "Authorization: Bearer slurry_sim_..."

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

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

  • GET/v1/accounts
  • GET/v1/analysisCategories
  • GET/v1/bankAccounts
  • POST/v1/bankAccounts
  • PUT/v1/bankAccounts/batch
  • GET/v1/bankAccounts/{id}
  • PUT/v1/bankAccounts/{id}
  • DELETE/v1/bankAccounts/{id}
  • GET/v1/bookTranTypes
  • GET/v1/cashPayments
  • POST/v1/cashPayments
  • PUT/v1/cashPayments/batch