Skip to content
Cloud infrastructure/devops

gitlab.com

GitLab sandbox and mock API

The platform for modern developers GitLab unifies issues, code review, CI and CD into a single UI Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
358
Collections
-
Event types
-
Start this simulation Vendor documentation
example request
curl https://your-gitlab.slurry.io/api/v3/application/settings \
  -H "Authorization: Bearer slurry_sim_..."

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

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

  • GET/v3/application/settings
  • PUT/v3/application/settings
  • POST/v3/ci/lint
  • GET/v3/deploy_keys
  • GET/v3/dockerfiles
  • GET/v3/dockerfiles/{name}
  • GET/v3/gitignores
  • GET/v3/gitignores/{name}
  • GET/v3/gitlab_ci_ymls
  • GET/v3/gitlab_ci_ymls/{name}
  • GET/v3/groups
  • POST/v3/groups