CMS Data Python API Docs | dltHub

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

Last updated:

The CMS Data API provides access to Medicare & Medicaid Services public data; it uses structured endpoints and supports filtering by dataset and columns. The Blue Button API offers claims data for Medicare enrollees, requiring authorization for access. The REST API base URL is https://data.cms.gov/data-api/v1 and Public data.cms.gov datasets do not require authentication; separate CMS APIs (Blue Button) require OAuth2 bearer tokens..

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 pip install "dlt[workspace]" and start loading CMS Data data in under 10 minutes.


What data can I load from CMS Data?

Here are some of the endpoints you can load from CMS Data:

ResourceEndpointMethodData selectorDescription
Dataset Datadataset/{uuid}/dataGETPrimary dataset rows; supports size & offset pagination and JSON:API filters.
Dataset Data Viewerdataset/{uuid}/data-viewerGETviewerMetadata for the dataset viewer.
Dataset Data Viewer Statsdataset/{uuid}/data-viewer/statsGETstatsStatistics about the dataset viewer.
Data Catalogdata.jsonGETresourcesPublic Open Data Catalog listing; contains an array of resource objects.
Provider Metastore Schemasprovider-data/api/1/metastore/datasetGETLists dataset schemas in the Provider Data catalog.

How do I authenticate with the CMS Data API?

Public data.cms.gov datasets are open; no authentication headers are required for requests.

1. Get your credentials

  1. For data.cms.gov public datasets: no credentials are needed; simply use the dataset UUID from the dataset overview page and call the endpoint.
  2. For Blue Button (if you require beneficiary‑level data): a) Register for a sandbox account at https://sandbox.bluebutton.cms.gov. b) In the sandbox dashboard, create an application to receive a client_id and client_secret. c) Follow the OAuth 2.0 Authorization Code flow described in the Blue Button docs to exchange the client credentials for a Bearer token. d) Use the token in the Authorization: Bearer <token> header for API calls.

2. Add them to .dlt/secrets.toml

[sources.cms_data_source] # data.cms.gov public datasets do not require credentials

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 venv && source .venv/bin/activate uv pip install "dlt[workspace]"

1. Install the dlt AI Workbench:

dlt 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:

dlt ai toolkit rest-api-pipeline install

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 CMS Data 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:

python cms_data_pipeline.py

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

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

Inspect your pipeline and data:

dlt pipeline cms_data_pipeline 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 dataset_data and data.json from the CMS Data 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 cms_data_source((none)=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://data.cms.gov/data-api/v1", "auth": { "type": "none", "(none)": (none), }, }, "resources": [ {"name": "dataset_data", "endpoint": {"path": "dataset/{uuid}/data"}}, {"name": "data_catalog", "endpoint": {"path": "data.json", "data_selector": "resources"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="cms_data_pipeline", destination="duckdb", dataset_name="cms_data_data", ) load_info = pipeline.run(cms_data_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("cms_data_pipeline").dataset() sessions_df = data.dataset_data.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM cms_data_data.dataset_data LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("cms_data_pipeline").dataset() data.dataset_data.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 CMS Data 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 Workbench:

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

Was this page helpful?

Community Hub

Need more dlt context for CMS Data?

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