Twinehealth Com Python API Docs | dltHub
Build a Twinehealth Com-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Twine Health's REST API is documented at https://redocly.github.io/redoc/?url=https://api.apis.guru/v2/specs/twinehealth.com/v7.78.1/openapi.json. It provides endpoints for managing AI Digital Twin data and metabolic health insights. The REST API base URL is https://api.twinehealth.com/pub and All requests require a Bearer token obtained via OAuth2..
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 Twinehealth Com data in under 10 minutes.
What data can I load from Twinehealth Com?
Here are some of the endpoints you can load from Twinehealth Com:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| patients | /pub/patients | GET | data | List patient records |
| providers | /pub/providers | GET | data | List provider records |
| appointments | /pub/appointments | GET | data | List appointment records |
| labs | /pub/labs | GET | data | List laboratory results |
| medications | /pub/medications | GET | data | List medication records |
How do I authenticate with the Twinehealth Com API?
Include an Authorization header with the value "Bearer <access_token>" on every request.
1. Get your credentials
- Log in to the Twinehealth developer portal (if available).\n2. Register a new application to obtain a client ID and client secret.\n3. Follow the OAuth2 token endpoint documentation to request an access token using the client credentials grant (POST to /oauth/token with client_id and client_secret).\n4. Store the returned access token in your dlt secrets.toml under the key defined by auth_token_key.
2. Add them to .dlt/secrets.toml
[sources.twinehealth_com_source] token = "your_access_token_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 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 Twinehealth Com 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 twinehealth_com_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline twinehealth_com_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset twinehealth_com_data The duckdb destination used duckdb:/twinehealth_com.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline twinehealth_com_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 patients and providers from the Twinehealth Com 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 twinehealth_com_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.twinehealth.com/pub", "auth": { "type": "bearer", "token": access_token, }, }, "resources": [ {"name": "patients", "endpoint": {"path": "patients", "data_selector": "data"}}, {"name": "providers", "endpoint": {"path": "providers", "data_selector": "data"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="twinehealth_com_pipeline", destination="duckdb", dataset_name="twinehealth_com_data", ) load_info = pipeline.run(twinehealth_com_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("twinehealth_com_pipeline").dataset() sessions_df = data.patients.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM twinehealth_com_data.patients LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("twinehealth_com_pipeline").dataset() data.patients.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 Twinehealth Com data to?
dlt supports loading into any of these destinations — only the destination parameter changes:
| Destination | Example 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 Twinehealth Com?
Request dlt skills, commands, AGENT.md files, and AI-native context.