Skip to content
Communication/messaging

statsocial.com

StatSocial Platform sandbox and mock API

API Reference: <br><br> The StatSocial API is organized around REST. Our API is designed to have predictable, resource-oriented URLs and to use HTTP response codes to indicate API errors. We use built-in HTTP features, like HTTP authentication and HTTP verbs, which can be understood by off-the-shelf HTTP clients, and we support cross-origin resource sharing to allow you to interact securely with o Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
17
Collections
-
Event types
-
Start this simulation
example request
curl https://your-statsocial.slurry.io/api/applications/status/ \
  -H "Authorization: Bearer slurry_sim_..."

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

  • GET/applications/status/
  • GET/reports/
  • POST/reports/
  • GET/reports/custom/create/
  • POST/reports/custom/create/
  • GET/reports/custom/generate/
  • POST/reports/custom/generate/
  • GET/reports/custom/insert/
  • POST/reports/custom/insert/
  • GET/reports/dates/
  • POST/reports/dates/
  • GET/reports/status/