Roost Python API Docs | dltHub

Roost is an AI‑powered test automation platform that generates and executes test plans and manages test events via a REST API. The REST API base URL is https://app.roost.ai/api and All requests require a Bearer token for authentication..

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

---

What data can I load from Roost?

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

---

How do I authenticate with the Roost API?

The API uses Bearer token authentication. Include the token in the Authorization header as: Authorization: Bearer for all protected endpoints.

1. Get your credentials

1. Sign in to your Roost account at https://app.roost.ai. 2) Open Account / Settings or API section (or Organization settings) in the web app. 3) Locate "API" or "API Keys" and create/generate a new personal API token. 4) Copy the token and store it securely (used as the Bearer token in Authorization header).

2. Add them to .dlt/secrets.toml

Copy
[sources.roost_source]
token = "your_roost_bearer_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 Roost 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 roost_pipeline.py

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

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

Inspect your pipeline and data:

Copy
dlt pipeline roost_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 tests and events from the Roost 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 roost_source(token=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://app.roost.ai/api",
            "auth": {
                "type": "bearer",
                "token": token,
            },
        },
        "resources": [
            {"name": "tests", "endpoint": {"path": "test"}},
            {"name": "events", "endpoint": {"path": "test/event"}}
        ],
    }
    yield from rest_api_resources(config)


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

SQL (DuckDB example):

Copy
SELECT * FROM roost_data.tests LIMIT 10;

In a marimo or Jupyter notebook:

Copy
import dlt

data = dlt.pipeline("roost_pipeline").dataset()
data.tests.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 Roost 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 or 403 Forbidden, verify your Authorization header is exactly: Authorization: Bearer <TOKEN>. Ensure the token is active, not expired, and has required permissions. Regenerate the key from account settings if needed.

Rate limits and 429 responses

The API may enforce rate limits; a 429 Too Many Requests indicates you should back off and retry after a delay. Implement exponential backoff and respect the Retry-After header if provided.

Pagination and result windowing

List endpoints accept query parameters such as take and skip (or similar) to page through results (see /test and /test/event query parameters). Use these to iterate through large result sets.

Common error payloads

Responses frequently return structured error objects with fields like code, timestamp, path, method, and message (e.g. { "code":404, "timestamp":"...", "path":"...", "method":"GET", "message":"Not found" }). Use these fields to surface meaningful error messages in pipelines.

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