Skip to content
Other

whapi.com:bets

Bets sandbox and mock API

The Bets API methods are used to place single, multiple and complex bets and to retrieve a customer’s bet history. When retrieving a customer’s bet history you can organize the bets from the betting history in terms of date, bet type and whether the bet is settled or not. You can also specify what fields to be included/excluded or return a list of all default fields the method returns. <br /><br / Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
6
Collections
-
Event types
-
Start this simulation
example request
curl https://your-whapi-bets.slurry.io/v2/bets/freebets \
  -H "Authorization: Bearer slurry_sim_..."

Your simulation gets its own hostname, key and IP allow-list. Built from API version 2.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

All 6.

  • POST/bet/complex
  • POST/bet/single
  • POST/betslips
  • GET/freebets
  • GET/history
  • PUT/{betId}/cashin