Skip to content
Banking/open banking

up.com.au

Up sandbox and mock API

The Up API gives you programmatic access to your balances and transaction data. You can request past transactions or set up webhooks to receive real-time events when new transactions hit your account. It’s new, it’s exciting and it’s just the beginning. Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
18
Collections
-
Event types
-
Start this simulation
example request
curl https://your-up-au.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 18.

  • GET/accounts
  • GET/accounts/{accountId}/transactions
  • GET/accounts/{id}
  • GET/categories
  • GET/categories/{id}
  • GET/tags
  • GET/transactions
  • GET/transactions/{id}
  • PATCH/transactions/{transactionId}/relationships/category
  • POST/transactions/{transactionId}/relationships/tags
  • DELETE/transactions/{transactionId}/relationships/tags
  • GET/util/ping