--- title: Buildkite API Integration on Truto slug: buildkite category: CI/CD canonical: "https://truto.one/integrations/detail/buildkite/" --- # Buildkite API Integration on Truto **Category:** CI/CD **Status:** Generally available ## Unified APIs ### Unified User Directory API - **Groups** — Groups are a collection of users in the source application. In some applications, they might also be called Teams. - **Me** — - **Organizations** — Organizations are the top level entity in the source application. Users are associated with an organization. - **Roles** — The Role object represents a role of a User. - **Users** — The User object represents a User. ## How it works 1. **Link your customer's Buildkite account.** Use Truto's frontend SDK; we handle every OAuth and API key flow so you don't need to create the OAuth app. 2. **Authentication is automatic.** Truto refreshes tokens, stores credentials securely, and injects them into every API request. 3. **Call Truto's API to reach Buildkite.** The Proxy API is a 1-to-1 mapping of the Buildkite API. 4. **Get a unified response format.** Every response uses a single shape, with cursor-based pagination and data in the `result` field. ## Use cases - **Sync Buildkite teams and users into your internal developer portal** — IDP platforms need to map engineering org structures to service ownership. By pulling Buildkite organizations, teams, and users through Truto's Unified User Directory API, your product can automatically reflect CI/CD ownership alongside service catalogs without manual configuration. - **Populate engineering analytics dashboards with org-level identity data** — Productivity and DORA metrics platforms need to attribute build outcomes to specific teams and individuals. Syncing Buildkite user and group data gives your product the identity layer required to break down deployment frequency and failure rates by team. - **Enforce role-based access compliance across CI/CD infrastructure** — Security and compliance SaaS products need visibility into who has access to what across a customer's toolchain. Pulling Buildkite roles, users, and organizations lets your product audit CI/CD access alongside other systems in a single normalized view. - **Automate team provisioning and deprovisioning in Buildkite** — Identity governance platforms can use Buildkite's user and group data to detect drift between an organization's identity provider and its CI/CD permissions, flagging orphaned accounts or misconfigured team memberships. ## What you can build - **Unified org chart with CI/CD team mapping** — Automatically sync Buildkite organizations, teams, and users into your product's org model so customers see their CI/CD team structure alongside data from HRIS, SCM, and other connected tools. - **Cross-platform access audit report** — Generate a consolidated report showing each user's roles across Buildkite and other connected platforms, highlighting over-permissioned accounts or users who should have been offboarded. - **Team-level CI/CD ownership dashboard** — Display which Buildkite groups own which pipelines by correlating user directory data with your product's service catalog, giving engineering leaders a clear ownership map. - **Real-time user directory sync for compliance workflows** — Continuously pull Buildkite user and role data to power automated compliance checks, ensuring that only authorized personnel retain access to production CI/CD pipelines. - **Identity-aware incident triage view** — Enrich incident management workflows by resolving Buildkite user identities so that on-call tools can automatically route CI/CD failures to the right team owner. ## FAQs ### What Buildkite data can I access through Truto today? Truto's Unified User Directory API supports syncing Buildkite Groups, Users, Roles, Organizations, and the authenticated user (Me). CI/CD-specific resources like Pipelines, Builds, and Jobs are not yet available as pre-built tools but can be built on request. ### How does authentication work for Buildkite integrations? Buildkite supports API token-based authentication. Your end users generate an API access token from their Buildkite account settings with the required scopes. Truto handles storing and managing these credentials securely on your behalf. ### Does Buildkite have rate limits I should be aware of? Yes. Buildkite's REST API enforces rate limits on a per-token basis. Truto manages pagination and respects these limits automatically so your integration doesn't get throttled during large data syncs. ### Can I request custom Buildkite tools beyond the Unified User Directory API? Absolutely. Truto builds integration tools on request. If you need access to Buildkite Pipelines, Builds, Jobs, Agents, or Annotations, Truto can build and expose those resources — typically covering both the REST v2 and GraphQL APIs that Buildkite offers. ### How does Truto normalize Buildkite's user and team data? Truto maps Buildkite-specific concepts like Organizations, Teams, and Members onto its Unified User Directory schema (Organizations, Groups, Users, Roles). This means your product code works the same way regardless of whether the underlying source is Buildkite, GitHub, or an HRIS system. ### Does Buildkite use a REST API or GraphQL API? Buildkite offers both a REST API (v2) and a GraphQL API. Buildkite recommends GraphQL for complex or nested queries. Truto abstracts this complexity — you interact with a single unified API regardless of which Buildkite API is used under the hood.