Skip to content
Cloud infrastructure/devops

runscope.com

Runscope sandbox and mock API

Manage Runscope programmatically. Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
29
Collections
-
Event types
-
Start this simulation
example request
curl https://your-runscope.slurry.io/account \
  -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 29.

  • GET/account
  • GET/buckets
  • POST/buckets
  • GET/buckets/{bucketKey}
  • DELETE/buckets/{bucketKey}
  • GET/buckets/{bucketKey}/environments
  • POST/buckets/{bucketKey}/environments
  • PUT/buckets/{bucketKey}/environments/{environmentId}
  • GET/buckets/{bucketKey}/errors
  • GET/buckets/{bucketKey}/messages
  • POST/buckets/{bucketKey}/messages
  • DELETE/buckets/{bucketKey}/messages