REST API overview

The Buildkite REST API aims to give you complete programmatic access and control of Buildkite to extend, integrate and automate anything to suit your particular needs.

The current version of the Buildkite API is v2.

For the list of existing disparities between the REST API and the GraphQL API, see API differences.


All API access is over HTTPS, and accessed from the domain. All data is sent as JSON.

  "response": "Hello World"

Query string parameters

Some API endpoints accept query string parameters which are added to the end of the URL. For example, the builds listing APIs can be filtered by state using the following curl command:

curl -H "Authorization: Bearer $TOKEN" \
  -X GET ""

Request body properties

Some API requests accept JSON request bodies for specifying data. For example, the build create API can be passed the required properties using the following curl command:

curl -H "Authorization: Bearer $TOKEN" \
  -X POST "" \
  -H "Content-Type: application/json" \
  -d '{
    "key": "value"

The data encoding is assumed to be application/json. Unless explicitly stated you can not encode properties as www-form-urlencoded or multipart/form-data.


You can authenticate with the Buildkite API using access tokens, represented by the value $TOKEN throughout this documentation.

API access tokens authenticate calls to the API and can be created from the API access tokens page. When configuring API access tokens, you can limit their access to individual organizations and permissions, and these tokens can be revoked at any time from the web interface or the REST API.

To authenticate an API call using an access token, set the Authorization HTTP header to the word Bearer, followed by a space, followed by the access token. For example:

curl -H "Authorization: Bearer $TOKEN" \
  -X GET ""

API access using basic HTTP authentication is not supported.


For endpoints which support pagination, the pagination information can be found in the Link HTTP response header containing zero or more of next, prev, first and last.

curl -i -H "Authorization: Bearer $TOKEN" \
  -X GET ""
HTTP/1.1 200 OK
Link: <>; rel="next", <>; rel="last"

You can set the page using the following query string parameters:

page The page of results to return

Default: 1

per_page How many results to return per-page

Default: 30

Maximum: 100

CORS headers

API responses include the following CORS headers allowing you to use the API directly from the browser:

  • Access-Controller-Allow-Origin: *
  • Access-Control-Expose-Headers: Link

For an example of this in use, see the Emojis API example on CodePen for adding emoji support to your own browser-based dashboards and build screens.

Migrating from v1 to v2

The following changes were made in v2 of our API:

  • POST /v1/organizations/{org.slug}/agents has been removed
  • DELETE /v1/organizations/{org.slug}/agents/{id} has been removed
  • All project-related properties in JSON responses and requests have been renamed to pipeline
  • The featured_build pipeline property has been removed
  • The deprecated /accounts URL has been removed
  • URLs containing /projects have been renamed to /pipelines


To make getting started easier, check out these clients available from our contributors: