Samsung Health Python API Docs | dltHub

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

Last updated:

Samsung Health provides a suite of APIs and SDKs allowing developers to integrate and access health data from Samsung Health, including a portal-based REST API for research platforms and SDKs for Android and wearable device data synchronization. The REST API base URL is http://localhost:3030/api and all requests require a 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 Samsung Health data in under 10 minutes.


What data can I load from Samsung Health?

Here are some of the endpoints you can load from Samsung Health:

ResourceEndpointMethodData selectorDescription
projects/projectsGETRetrieve all project lists.
project_details/projects/{projectId}GETRetrieve information for a specific project.
project_tasks/projects/{projectId}/tasksGETRetrieve a list of tasks.
task_details/projects/{projectId}/tasks/{taskId}GETRetrieve tasks with a specific task_id.
in_lab_visits/projects/{projectId}/in-lab-visitsGETRetrieve a list of in-lab visits.
in_lab_visit_details/projects/{projectId}/in-lab-visits/{inLabVisitId}GETRetrieve in-lab visits with a specific inLabVisitId.
account_users/account-service/usersGETRetrieves a list of users.

How do I authenticate with the Samsung Health API?

Authentication uses OAuth 2.0 with the authorization code flow, requiring a bearer token passed in the Authorization header. Applications must exchange an authorization code for access and refresh tokens at a designated Samsung token endpoint.

1. Get your credentials

Samsung Health is not a self-serve platform; you must apply for access to their developer programs via the Samsung Developers portal. The application process requires submitting a formal partnership request, which includes details about your organization, intended use cases, data requirements, and security protocols. Upon approval, which typically takes 5-15 business days, Samsung will provision the required client_id and client_secret credentials for your project. Do not store these credentials in client-side code; keep them secured in your backend environment.

2. Add them to .dlt/secrets.toml

[sources.samsung_health_source] client_id = "your_samsung_client_id" client_secret = "your_samsung_client_secret"

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 Samsung Health 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 samsung_health_pipeline.py

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

Pipeline samsung_health_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset samsung_health_data The duckdb destination used duckdb:/samsung_health.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 account-service/signin and data-query-service/sql from the Samsung Health 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 samsung_health_source(client_id=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "http://localhost:3030/api", "auth": {"type": "bearer", "token": client_id}, }, "resources": [ {"name": "projects", "endpoint": {"path": "projects"}}, {"name": "project_tasks", "endpoint": {"path": "projects/{projectId}/tasks"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="samsung_health_pipeline", destination="duckdb", dataset_name="samsung_health_data", ) load_info = pipeline.run(samsung_health_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("samsung_health_pipeline").dataset() sessions_df = data.projects.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM samsung_health_data.projects LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("samsung_health_pipeline").dataset() data.projects.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 Samsung Health 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 Samsung Health?

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

Available Pipelines