Skip to content
Cloud infrastructure/devops

github.com

GitHub sandbox and mock API

GitHub's v3 REST API. Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
350
Collections
-
Event types
-
Start this simulation Vendor documentation
example request
curl https://your-github.slurry.io/ \
  -H "Authorization: Bearer slurry_sim_..."

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

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

  • GET/
  • GET/app
  • POST/app-manifests/{code}/conversions
  • GET/app/hook/config
  • PATCH/app/hook/config
  • GET/app/hook/deliveries
  • GET/app/hook/deliveries/{delivery_id}
  • POST/app/hook/deliveries/{delivery_id}/attempts
  • GET/app/installations
  • GET/app/installations/{installation_id}
  • DELETE/app/installations/{installation_id}
  • POST/app/installations/{installation_id}/access_tokens
GitHub sandbox and mock API | Slurry