Healthie Python API Docs | dltHub

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

Last updated:

Healthie is a comprehensive GraphQL API platform for healthcare providers to manage appointments, billing, charting, and patient care workflows. The REST API base URL is https://api.gethealthie.com/graphql and all requests require Basic Authorization header with API key and AuthorizationSource 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 Healthie data in under 10 minutes.


What data can I load from Healthie?

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

ResourceEndpointMethodData selectorDescription
appointments/graphqlPOSTappointmentsFetch paginated appointment collection.
entries/graphqlPOSTentriesFetch paginated entries collection.
users/graphqlPOSTusersFetch paginated users collection.
documents/graphqlPOSTdocumentsFetch paginated documents collection.
course_memberships/graphqlPOSTcourseMembershipsFetch paginated course memberships.

How do I authenticate with the Healthie API?

Healthie uses API key-based authentication requiring an 'Authorization: Basic <API_KEY>' header and an 'AuthorizationSource: API' header in all requests. Some users may also require an 'AuthorizationShard: <SHARD_ID>' header.

1. Get your credentials

To obtain API credentials for Healthie, you must first have an active Group or Enterprise plan with API access enabled. Log in to your Healthie account (Production or Sandbox environment), navigate to Settings > Developer > API Key, and select Add API Key to generate a new key. Ensure your user account has the permission 'Can view and manage developer features (Webhooks, API keys, etc)' enabled within the Organization > Members settings. For programmatic generation, you can use the createApiKey GraphQL mutation.

2. Add them to .dlt/secrets.toml

[sources.healthie_source] api_key = "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 Healthie 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 healthie_pipeline.py

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

Pipeline healthie_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset healthie_data The duckdb destination used duckdb:/healthie.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 Healthie uses a single GraphQL endpoint for all operations, typically https://api.gethealthie.com/graphql for production and https://sandbox.api.gethealthie.com/graphql for development. The API is strictly GraphQL; there are no REST endpoints. from the Healthie 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 healthie_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.gethealthie.com/graphql", "auth": {"type": "http_basic", "username": "REPLACE_ME", "password": api_key}, }, "resources": [ {"name": "entries", "endpoint": {"path": "graphql", "data_selector": "entries"}}, {"name": "appointments", "endpoint": {"path": "graphql", "data_selector": "appointments"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="healthie_pipeline", destination="duckdb", dataset_name="healthie_data", ) load_info = pipeline.run(healthie_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("healthie_pipeline").dataset() sessions_df = data.entries.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM healthie_data.entries LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("healthie_pipeline").dataset() data.entries.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 Healthie 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 Healthie?

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

Available Pipelines