Skip to content
Project management & work tracking

docs.gitlab.com

GitLab sandbox and mock API

GitLab REST API used to interact with a GitLab installation. Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
600
Collections
-
Event types
-
Start this simulation Vendor documentation
example request
curl https://your-gitlab-2.slurry.io/api/v4/orbit/query/templates \
  -H "Authorization: Bearer slurry_sim_..."

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

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

  • GET/api/v4/namespaces/{id}/gitlab_subscription
  • POST/api/v4/namespaces/{id}/gitlab_subscription
  • PUT/api/v4/namespaces/{id}/gitlab_subscription
  • POST/api/v4/namespaces/{id}/minutes
  • PATCH/api/v4/namespaces/{id}/minutes/move/{target_id}
  • GET/api/v4/namespaces/{id}/subscription_add_on_purchase/{add_on_name}
  • POST/api/v4/namespaces/{id}/subscription_add_on_purchase/{add_on_name}
  • PUT/api/v4/namespaces/{id}/subscription_add_on_purchase/{add_on_name}
  • GET/api/v4/internal/gitlab_subscriptions/namespaces/{id}/projects
  • POST/api/v4/rollouts/{id}
  • POST/api/v4/orbit/query
  • POST/api/v4/orbit/query/{name}