How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Buildkite Builds API

The Builds API from Buildkite — 6 operation(s) for builds.

Buildkite Builds API is one of 20 APIs that Buildkite publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Builds. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 7 operations across 6 paths, and defines 6 schemas. It is described by OpenAPI 3.2.0, at version 2.0.

Requests are made against a single base URL, https://api.buildkite.com/v2.

7 operations 6 paths 6 schemas 4 GET1 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0
Base URL
https://api.buildkite.com/v2
Authentication
HTTP Bearer
Contact
Resource Areas
1

Authentication & Security 1

Buildkite Builds API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — Bearer token issued from your Buildkite Personal Access Tokens page.

Paths & Operations 7

Across 6 paths, the API surfaces 7 operations — 4 GET, 1 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

Builds 7
GET
/builds
List all builds
listAllBuilds → 200
GET
/organizations/{org}/builds
List org builds
listOrgBuilds 1 param → 200
GET
/organizations/{org}/pipelines/{slug}/builds
List pipeline builds
listPipelineBuilds 2 params → 200
POST
/organizations/{org}/pipelines/{slug}/builds
Create build
createBuild 2 params body → 201
GET
/organizations/{org}/pipelines/{slug}/builds/{number}
Get build
getBuild 3 params → 200
PUT
/organizations/{org}/pipelines/{slug}/builds/{number}/cancel
Cancel build
cancelBuild 3 params → 200
PUT
/organizations/{org}/pipelines/{slug}/builds/{number}/rebuild
Rebuild
rebuildBuild 3 params → 200

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are Job (20 properties), Build (18 properties), Pipeline (16 properties), Agent (14 properties). Each schema is shown below with its type and property counts.

BuildCreate
object
10 properties 2 required
Job
object
20 properties
Build
object
18 properties
User
object
6 properties
Pipeline
object
16 properties
Agent
object
14 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

buildkite-builds-api-openapi.yml Raw ↑

Other APIs Buildkite publishes across the network.

Buildkite REST API
Buildkite GraphQL API
Buildkite Agent API
Buildkite AccessToken API
Buildkite Agents API
Buildkite AgentTokens API
Buildkite Annotations API
Buildkite Artifacts API
Buildkite Clusters API
Buildkite Emojis API
Buildkite Jobs API
Buildkite Meta API
Where this information came from

This is an independent, third-party profile of Buildkite Builds API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.