Epic Tapestry Python API Docs | dltHub

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

Last updated:

Epic Tapestry is a payer-focused managed care administration system that provides web services for interoperability and operational workflows within the Epic ecosystem. The REST API base URL is https://fhir.epic.com/interconnect-fhir-oauth/api/FHIR/R4 and all requests require an OAuth 2.0 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 Epic Tapestry data in under 10 minutes.


What data can I load from Epic Tapestry?

Here are some of the endpoints you can load from Epic Tapestry:

ResourceEndpointMethodData selectorDescription
users/usersGETRetrieve a list of users
projects/projectsGETRetrieve a list of projects
tasks/tasksGETRetrieve a list of tasks
organizations/organizationsGETRetrieve a list of organizations
teams/teamsGETRetrieve a list of teams

How do I authenticate with the Epic Tapestry API?

Epic web services use OAuth 2.0. The request must include an Authorization header with a Bearer token, which is obtained via an authorization flow using a client ID issued by Epic.

1. Get your credentials

Epic does not provide a single dashboard-generated API key for all services. Integration with Epic systems (including those involving Tapestry managed care data) typically requires registering an application on the Epic on FHIR developer portal. 1) Register as a developer on the Epic on FHIR website. 2) Create a new app entry in the 'Build Apps' section. 3) For secure production integrations, configure the app as a confidential client and upload a public key (X.509 certificate) or provide a client secret if supported by the specific interface agreement. 4) Use the assigned Client ID to initiate OAuth 2.0 flows to obtain access tokens. Contact open@epic.com if specific web services need to be enabled for your App ID.

2. Add them to .dlt/secrets.toml

[sources.epic_tapestry_source] client_id = "your_epic_client_id_here" client_secret = "your_client_secret_if_applicable" # For OAuth2, use client_id and/or client_secret as required by the specific Epic interface flow.

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 Epic Tapestry 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 epic_tapestry_pipeline.py

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

Pipeline epic_tapestry_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset epic_tapestry_data The duckdb destination used duckdb:/epic_tapestry.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 token and fhir from the Epic Tapestry 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 epic_tapestry_source(client_id=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://fhir.epic.com/interconnect-fhir-oauth/api/FHIR/R4", "auth": {"type": "bearer", "token": client_id}, }, "resources": [ {"name": "users", "endpoint": {"path": "users", "data_selector": "data"}}, {"name": "projects", "endpoint": {"path": "projects", "data_selector": "data"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="epic_tapestry_pipeline", destination="duckdb", dataset_name="epic_tapestry_data", ) load_info = pipeline.run(epic_tapestry_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("epic_tapestry_pipeline").dataset() sessions_df = data.users.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM epic_tapestry_data.users LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("epic_tapestry_pipeline").dataset() data.users.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 Epic Tapestry 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 Epic Tapestry?

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