Get started making authenticated queries against Buildkite's GraphQL API: the endpoint, token permission, the interactive explorer, and how to address organizations/pipelines by slug or global ID.

Documented steps

1. Endpoint: all requests are HTTP `POST` to `https://graphql.buildkite.com/v1` with an `application/json`-encoded body containing a `"query"` key and optionally a `"variables"` key. See https://buildkite.com/docs/apis/graphql-api
2. Auth: send header `Authorization: Bearer <token>`, where the token was created/edited at https://buildkite.com/user/api-access-tokens with the **Enable GraphQL API Access** permission checked (GraphQL tokens' access can't be scope-restricted the way REST tokens can).
3. Explorer: use the interactive GraphQL console at https://buildkite.com/user/graphql/console — its **Documentation** tab renders the full live schema for browsing types/fields.
4. Example query — current user: `curl https://graphql.buildkite.com/v1 -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" -d '{"query": "{ viewer { user { name } } }"}'`.
5. Address an organization by slug: `query { organization(slug: "my-org") { id } }`. Address a pipeline by its combined `org-slug/pipeline-slug` form: `query { pipeline(slug: "my-org/my-pipeline") { id } }` (see https://buildkite.com/docs/apis/graphql/cookbooks/pipelines).
6. Every object also has a permanent global `id`; fetch it once via a slug query, then re-fetch directly with `query { node(id: "<graphql id>") { ... on Organization { pipelines { count } } } }` using an inline fragment for the concrete type.
7. To find a pipeline's stable `uuid` (survives renames, unlike slug) by partial slug: `query { organization(slug: "my-org") { pipelines(first: 50, search: "part-of-slug") { edges { node { slug uuid } } } } }`.
8. Docs used: https://buildkite.com/docs/apis/graphql-api and https://buildkite.com/docs/apis/graphql/cookbooks/pipelines