Logfire Python API Docs | dltHub

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

Last updated:

Logfire is an observability tool providing a REST API for managing organizational resources, querying data, and accessing audit logs. The REST API base URL is https://api-us.pydantic.dev/api or https://api-eu.pydantic.dev/api (or specific regional endpoints for query services) and all requests require a Bearer token in the Authorization header.

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


What data can I load from Logfire?

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

ResourceEndpointMethodData selectorDescription
audit_logs/v1/audit-logs/GETRetrieve organization audit log entries.
audit_log/v1/audit-logs/{audit_log_id}/GETRetrieve a specific audit log entry by ID.
query/v2/queryPOSTExecute arbitrary SQL queries against project data.

How do I authenticate with the Logfire API?

All API requests require an Authorization header with the value 'Bearer ', where the token is either a read token, write token, or API key depending on the specific endpoint being accessed.

1. Get your credentials

To obtain an API key for Logfire, navigate to the Logfire web console. Depending on your needs, you can generate keys at the organization or project level: 1. Log in to your Logfire account at logfire.pydantic.dev. 2. To generate an organization-level key, click your organization name in the bottom-left sidebar, then select 'Org settings', and navigate to 'API Keys'. To generate a project-level key, open the specific project, go to 'Settings', and navigate to 'API Keys'. 3. Click '+ New API key'. 4. Provide a name and select the appropriate scopes for your use case (e.g., read, write). 5. Click 'Create'. The API key is displayed only once; copy it immediately and store it securely, as it will not be shown again.

2. Add them to .dlt/secrets.toml

[sources.logfire_source] # Inside .dlt/secrets.toml read_token = "pylf_v2_..."

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 Logfire 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 logfire_pipeline.py

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

Pipeline logfire_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset logfire_data The duckdb destination used duckdb:/logfire.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 records and metrics from the Logfire 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 logfire_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api-us.pydantic.dev/api or https://api-eu.pydantic.dev/api (or specific regional endpoints for query services)", "auth": {"type": "bearer", "token": api_key}, }, "resources": [ {"name": "query", "endpoint": {"path": "v2/query", "data_selector": "rows"}}, {"name": "audit_logs", "endpoint": {"path": "v1/audit-logs/", "data_selector": "logs"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="logfire_pipeline", destination="duckdb", dataset_name="logfire_data", ) load_info = pipeline.run(logfire_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("logfire_pipeline").dataset() sessions_df = data.query.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM logfire_data.query LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("logfire_pipeline").dataset() data.query.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 Logfire 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 Logfire?

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

Available Pipelines