Definitive Healthcare Python API Docs | dltHub

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

Last updated:

Definitive Healthcare is a healthcare intelligence platform providing RESTful APIs for accessing facility, provider, and expert data. The REST API base URL is https://api.defhc.com/v4/odata-v4 and all requests require a Bearer token obtained from an OAuth2-style password grant flow.

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


What data can I load from Definitive Healthcare?

Here are some of the endpoints you can load from Definitive Healthcare:

ResourceEndpointMethodData selectorDescription
executivesodata-v4/ExecutivesGETProvides information about executives.
news_itemsodata-v4/NewsItemsGETAccesses news items related to the organization or hospitals.
hospitalsodata-v4/HospitalsGETProvides a list of hospitals.
hospitals_with_executivesodata-v4/Hospitals?$expand=ExecutivesGETRetrieves hospitals with associated executives.
reportsReportsGETRetrieves custom or saved reports.

How do I authenticate with the Definitive Healthcare API?

Authentication requires a POST request to the /v4/token endpoint using application/x-www-form-urlencoded data containing username, password, and grant_type='password'. Once an access token is retrieved, it must be passed in subsequent requests as a Bearer token in the Authorization header.

1. Get your credentials

To obtain API credentials, contact your Definitive Healthcare account representative to request access to the API. Credentials consist of a unique username and password assigned by the company. These are used to authenticate via the OpenID standard by sending a POST request to the /v4/token endpoint with the parameters grant_type=password, your assigned username, and password. The response will provide an access token required for all subsequent data requests.

2. Add them to .dlt/secrets.toml

[sources.definitive_healthcare_source] access_token = "REPLACE_ME"

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 Definitive Healthcare 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 definitive_healthcare_pipeline.py

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

Pipeline definitive_healthcare_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset definitive_healthcare_data The duckdb destination used duckdb:/definitive_healthcare.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 /v4/token and /v4/odata-v4/Hospitals from the Definitive Healthcare 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 definitive_healthcare_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.defhc.com/v4/odata-v4", "auth": {"type": "bearer", "token": access_token}, }, "resources": [ {"name": "executives", "endpoint": {"path": "odata-v4/Executives"}}, {"name": "news_items", "endpoint": {"path": "odata-v4/NewsItems"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="definitive_healthcare_pipeline", destination="duckdb", dataset_name="definitive_healthcare_data", ) load_info = pipeline.run(definitive_healthcare_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("definitive_healthcare_pipeline").dataset() sessions_df = data.executives.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM definitive_healthcare_data.executives LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("definitive_healthcare_pipeline").dataset() data.executives.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 Definitive Healthcare 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 Definitive Healthcare?

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

Available Pipelines