PostHog Python API Docs | dltHub

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

Last updated:

PostHog is an open-source product analytics and event platform that provides a REST API for querying, creating, and managing data objects like dashboards, insights, and project configurations. The REST API base URL is https://us.posthog.com/api/ or https://eu.posthog.com/api/ (or your self-hosted instance URL) and all private API requests require authentication via personal API key using Bearer token or parameter 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 add "dlt[hub]" and start loading PostHog data in under 10 minutes.


What data can I load from PostHog?

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

ResourceEndpointMethodData selectorDescription
projects/api/projects/GETList all projects.
dashboards/api/environments/
/dashboards/
GETresultsList all dashboards for an environment.
feature_flags/api/projects/
/feature_flags/
GETresultsList all feature flags for a project.
insights/api/projects/
/insights/
GETresultsList all insights for a project.
hog_functions/api/projects/
/hog_functions/
GETresultsList all hog functions for a project.

How do I authenticate with the PostHog API?

Authentication is performed by passing a personal API key in an Authorization header using the Bearer scheme, e.g., 'Authorization: Bearer <your_personal_api_key>'. Alternative methods include providing the key in the request body as 'personal_api_key' or as a query string parameter.

1. Get your credentials

To obtain a personal API key for the PostHog REST API: 1. Log in to your PostHog instance. 2. Click your avatar icon in the bottom left corner and select 'Account settings'. 3. Navigate to the 'Personal API Keys' tab. 4. Click '+ Create a personal API Key'. 5. Assign a descriptive label and select the required scopes (best practice is to select only what is needed). 6. Click 'Create key'. 7. Copy the key value immediately; it will not be displayed again.

2. Add them to .dlt/secrets.toml

[sources.posthog_source] personal_api_key = "your_personal_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 PostHog 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 posthog_pipeline.py

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

Pipeline posthog_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset posthog_data The duckdb destination used duckdb:/posthog.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 'api/projects/

/insights/ and api/projects/
/persons/' from the PostHog 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 posthog_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://us.posthog.com/api/ or https://eu.posthog.com/api/ (or your self-hosted instance URL)", "auth": {"type": "bearer", "token": api_key}, }, "resources": [ {"name": "dashboards", "endpoint": {"path": "api/environments/{environment_id}/dashboards/", "data_selector": "results"}}, {"name": "hog_functions", "endpoint": {"path": "api/projects/{project_id}/hog_functions/", "data_selector": "results"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="posthog_pipeline", destination="duckdb", dataset_name="posthog_data", ) load_info = pipeline.run(posthog_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("posthog_pipeline").dataset() sessions_df = data.dashboards.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM posthog_data.dashboards LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("posthog_pipeline").dataset() data.dashboards.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 PostHog 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 PostHog?

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