Skip to content
Cloud infrastructure/devops

api.buildkite.com

Buildkite sandbox and mock API

All endpoints are served under the `/v2/analytics` path prefix. ## Authentication Most endpoints authenticate with a Buildkite API access token passed as a Bearer token. A subset of endpoints (suite `show`) additionally accept OIDC tokens issued to a Pipeline build. When authenticated via OIDC, scope checks are made against the OIDC policy rather than the access token's scopes. Each endpoint en Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
24
Collections
-
Event types
-
Start this simulation Vendor documentation
example request
curl https://your-buildkite.slurry.io/v2/analytics/organizations/123/pipelines/123/suites \
  -H "Authorization: Bearer slurry_sim_..."

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

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

  • GET/organizations/{org}/pipelines/{pipeline_slug}/suites
  • GET/organizations/{org}/suites
  • POST/organizations/{org}/suites
  • GET/organizations/{org}/suites/{slug}
  • PUT/organizations/{org}/suites/{slug}
  • PATCH/organizations/{org}/suites/{slug}
  • DELETE/organizations/{org}/suites/{slug}
  • GET/organizations/{org}/suites/{suite_slug}/tests
  • GET/organizations/{org}/suites/{suite_slug}/tests/{id}
  • GET/organizations/{org}/suites/{suite_slug}/tests/skipped
  • GET/organizations/{org}/suites/{suite_slug}/tests/muted
  • POST/organizations/{org}/suites/{suite_slug}/tests/find