Bart Python API Docs | dltHub

BART is a public transit API providing station, schedule, route, real‑time estimated departures (ETD), and service advisory data for the Bay Area Rapid Transit system. The REST API base URL is https://api.bart.gov/api and Requests require a validation API key passed as a query parameter..

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 Bart data in under 10 minutes.

---

What data can I load from Bart?

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

---

How do I authenticate with the Bart API?

The legacy BART API uses a single validation key supplied as the key query parameter on each request (key=YOUR_KEY). JSON responses are requested by adding json=y. No OAuth is used.

1. Get your credentials

1. Visit the BART developer pages and read the Developer License Agreement (https://www.bart.gov/schedules/developers/developer-license-agreement). 2) Register for a validation key via the BART API registration on the developer pages (links from https://api.bart.gov/docs/overview/index.aspx). 3) Receive the validation key by email or via the registration confirmation and use it as the key query parameter.

2. Add them to .dlt/secrets.toml

Copy
[sources.bart_source]
api_key = "your_bart_api_key_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 Bart 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 bart_pipeline.py

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

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

Inspect your pipeline and data:

Copy
dlt pipeline bart_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 etd and station_list from the Bart 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 bart_source(api_key=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://api.bart.gov/api",
            "auth": {
                "type": "api_key",
                "key": api_key,
            },
        },
        "resources": [
            {"name": "etd", "endpoint": {"path": "api/etd.aspx", "data_selector": "root.station"}},
            {"name": "station_list", "endpoint": {"path": "api/stn.aspx", "data_selector": "root.stations.station"}}
        ],
    }
    yield from rest_api_resources(config)


def get_data() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="bart_pipeline",
        destination="duckdb",
        dataset_name="bart_data",
    )
    load_info = pipeline.run(bart_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("bart_pipeline").dataset()
sessions_df = data.etd.df()
print(sessions_df.head())

SQL (DuckDB example):

Copy
SELECT * FROM bart_data.etd LIMIT 10;

In a marimo or Jupyter notebook:

Copy
import dlt

data = dlt.pipeline("bart_pipeline").dataset()
data.etd.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 Bart 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 requests return errors or only minimal data, verify you included your validation key as the key query parameter (key=YOUR_KEY) and json=y for JSON output. Ensure the key is active and not expired per the Developer License Agreement.

Rate limits and usage

The legacy API is intended for light developer use; adhere to the Developer License Agreement. If you receive HTTP 429 or truncated responses, reduce request frequency. Prefer GTFS/GTFS-RT feeds for bulk or production real‑time ingestion.

JSON response structure and selectors

Most JSON responses are wrapped under a top‑level root object. Common selectors: station lists → root.stations.station; station detail/ETD → root.station (contains etd array); routes list → root.routes.route; advisories → root.bsa.

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