Skip to content
Cloud infrastructure/devops

gamesparks.net:game-details

GameSparks Game Details sandbox and mock API

The API to manage the GameSparks game details Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
76
Collections
-
Event types
-
example request
curl https://your-gamesparks-game-details.slurry.io/restv2/game/regions \
  -H "Authorization: Bearer slurry_sim_..."

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

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

  • GET/restv2/game/regions
  • GET/restv2/game/{apiKey}/admin/analytics
  • GET/restv2/game/{apiKey}/admin/analytics/count
  • GET/restv2/game/{apiKey}/admin/analytics/rollingRetention
  • GET/restv2/game/{apiKey}/admin/billingDetails
  • PUT/restv2/game/{apiKey}/admin/billingDetails
  • GET/restv2/game/{apiKey}/admin/notifications/summary
  • POST/restv2/game/{apiKey}/admin/pushNotifications/test/amazon
  • POST/restv2/game/{apiKey}/admin/pushNotifications/test/apple/development
  • POST/restv2/game/{apiKey}/admin/pushNotifications/test/apple/production
  • POST/restv2/game/{apiKey}/admin/pushNotifications/test/google
  • POST/restv2/game/{apiKey}/admin/pushNotifications/test/microsoft/windows8