Buildkite Python API Docs | dltHub

Buildkite is a CI/CD platform that provides REST and Agent APIs to manage organizations, pipelines, builds, jobs, agents, artifacts, and related resources programmatically. The REST API base URL is https://api.buildkite.com/v2 and all requests require a Bearer access token.

dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv pip install "dlt[workspace]" and start loading Buildkite data in under 10 minutes.

---

What data can I load from Buildkite?

Here are some of the endpoints you can load from Buildkite:

---

How do I authenticate with the Buildkite API?

Authentication uses Buildkite API access tokens. Set the Authorization header to "Bearer " for all REST API requests.

1. Get your credentials

1. Sign in to Buildkite. 2) Go to User settings → API access tokens (https://buildkite.com/user/api-access-tokens). 3) Create a new access token and select the required scopes (e.g., read_builds, read_pipelines). 4) Copy the generated token and store it securely. 5) Use the token in the Authorization: Bearer header for API calls.

2. Add them to .dlt/secrets.toml

Copy
[sources.buildkite_source]
access_token = "your_buildkite_token_here"

dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.

---

How do I set up and run the pipeline?

Set up a virtual environment and install dlt:

Copy
uv venv && source .venv/bin/activate
uv pip install "dlt[workspace]"

1. Install the dlt AI Workbench:

Copy
dlt ai init --agent <your-agent> # <agent>: claude | cursor | codex

This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →

2. Install the rest-api-pipeline toolkit:

Copy
dlt ai toolkit rest-api-pipeline install

This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →

3. Start LLM-assisted coding:

Use /find-source to load data from the Buildkite API into DuckDB.

The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.

4. Run the pipeline:

Copy
python buildkite_pipeline.py

If everything is configured correctly, you'll see output like this:

Copy
Pipeline buildkite_pipeline load step completed in 0.26 seconds
1 load package(s) were loaded to destination duckdb and into dataset buildkite_data
The duckdb destination used duckdb:/buildkite.duckdb location to store data
Load package 1749667187.541553 is LOADED and contains no failed jobs

Inspect your pipeline and data:

Copy
dlt pipeline buildkite_pipeline show

This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.

---

Python pipeline example

This example loads builds and pipelines from the Buildkite API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

Copy
import dlt
from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources

@dlt.source
def buildkite_source(access_token=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://api.buildkite.com/v2",
            "auth": {
                "type": "bearer",
                "token": access_token,
            },
        },
        "resources": [
            {"name": "builds", "endpoint": {"path": "organizations/{org.slug}/pipelines/{pipeline.slug}/builds", "data_selector": "builds"}},
            {"name": "pipelines", "endpoint": {"path": "organizations/{org.slug}/pipelines", "data_selector": "pipelines"}}
        ],
    }
    yield from rest_api_resources(config)


def get_data() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="buildkite_pipeline",
        destination="duckdb",
        dataset_name="buildkite_data",
    )
    load_info = pipeline.run(buildkite_source())
    print(load_info)

To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.

---

How do I query the loaded data?

Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.

Python (pandas DataFrame):

Copy
import dlt

data = dlt.pipeline("buildkite_pipeline").dataset()
sessions_df = data.builds.df()
print(sessions_df.head())

SQL (DuckDB example):

Copy
SELECT * FROM buildkite_data.builds LIMIT 10;

In a marimo or Jupyter notebook:

Copy
import dlt

data = dlt.pipeline("buildkite_pipeline").dataset()
data.builds.df().head()

See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.

---

What destinations can I load Buildkite data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.

---

Troubleshooting

Authentication failures

If you receive 401 Unauthorized, verify the Authorization header is present and formatted as "Authorization: Bearer " and that the token has the required scopes. Tokens can be revoked; check https://buildkite.com/user/api-access-tokens.

Rate limiting / pagination

Responses are paginated and include Link headers (rel="next","prev","first","last"). Use the page and per_page query parameters (default per_page=30, max 100). Check the Link header to iterate pages; list endpoints return top‑level arrays under keys such as "builds" or "pipelines".

Common errors

• 400 Bad Request — invalid parameters.
• 401 Unauthorized — missing or invalid token.
• 403 Forbidden — insufficient token scopes or access to resource.
• 404 Not Found — invalid resource identifiers.
• 429 Too Many Requests — rate limiting; back off and retry.
• 500/502/503 — transient server errors, retry with backoff.

Ensure that the API key is valid to avoid 401 Unauthorized errors. Also, verify endpoint paths and parameters to avoid 404 Not Found errors.

---

Next steps

Continue your data engineering journey with the other toolkits of the dltHub AI Workbench:

• data-exploration — Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.
• dlthub-runtime — Deploy, schedule, and monitor your pipeline in production.

Copy
dlt ai toolkit data-exploration install
dlt ai toolkit dlthub-runtime install

• How to deploy a pipeline
• How to explore your data in marimo Notebooks
• How to query your data in Python with dataset
• Join the dlt community on Slack