Ghost inspector Python API Docs | dltHub

Build a Ghost inspector-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.

Last updated:

Ghost Inspector is a web UI testing and monitoring platform that runs browser-based tests and provides a public REST API to manage and retrieve tests, suites, and execution results. The REST API base URL is https://api.ghostinspector.com/v1 and all requests require an apiKey parameter to be provided in the query string or request body.

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 add "dlt[hub]" and start loading Ghost inspector data in under 10 minutes.


What data can I load from Ghost inspector?

Here are some of the endpoints you can load from Ghost inspector:

ResourceEndpointMethodData selectorDescription
tests/tests/GETdataList all tests in the account
test/tests/{testId}/GETdataGet a single test's details
suites/suites/GETdataList all suites in the account
suite/suites/{suiteId}/GETdataGet a single suite's details
test_results/tests/{testId}/results/GETdataList test results for a specific test
suite_results/suites/{suiteId}/results/GETdataList suite results for a specific suite
folders/folders/GETdataList all folders in the account
folder/folders/{folderId}/GETdataGet a single folder's details
result/results/{resultId}/GETdataGet a single test result's details

How do I authenticate with the Ghost inspector API?

Authentication is performed by including an 'apiKey' parameter in the request, typically via the query string or within the request body. No specific HTTP headers are required for authentication.

1. Get your credentials

To obtain your Ghost Inspector API credentials, sign in to your Ghost Inspector account at https://app.ghostinspector.com. Navigate to your Account Settings (typically found in the top-right user menu) and look for the section labeled 'API Access'. You can copy your personal API key from this page. You have the option to regenerate this key at any time, which will immediately invalidate the previous key.

2. Add them to .dlt/secrets.toml

[sources.ghost_inspector_source] api_key = "your_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:

uv init uv add "dlt[hub]"

1. Install the dlt AI harness:

uv run dlthub 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:

uv run dlthub ai toolkit install rest-api-pipeline

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 Ghost inspector 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:

uv run python ghost_inspector_pipeline.py

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

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

Inspect your pipeline and data:

uv run dlthub 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 suites/ from the Ghost inspector API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def ghost_inspector_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.ghostinspector.com/v1", "auth": {"type": "api_key", "api_key": api_key, "name": "apiKey", "location": "query"}, }, "resources": [ {"name": "tests", "endpoint": {"path": "tests/", "data_selector": "data"}}, {"name": "suites", "endpoint": {"path": "suites/", "data_selector": "data"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="ghost_inspector_pipeline", destination="duckdb", dataset_name="ghost_inspector_data", ) load_info = pipeline.run(ghost_inspector_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):

import dlt data = dlt.pipeline("ghost_inspector_pipeline").dataset() sessions_df = data.tests.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM ghost_inspector_data.tests LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("ghost_inspector_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 Ghost inspector data to?

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

DestinationExample value
DuckDB (local, default)"duckdb"
PostgreSQL"postgres"
BigQuery"bigquery"
Snowflake"snowflake"
Redshift"redshift"
Databricks"databricks"
Filesystem (S3, GCS, Azure)"filesystem"

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


Next steps

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

  • data-exploration — Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.
  • dlthub-platform — Deploy, schedule, and monitor your pipeline in production.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform

Was this page helpful?

Community Hub

Need more dlt context for Ghost inspector?

Request dlt skills, commands, AGENT.md files, and AI-native context.