# Collect many users' wearable data into a product's backend

> Collect many users' wearable data into a product's backend: 2 companies fully do it, 1 with a limit, 9 carry the tag. Every listing in Health records & wellness data with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/health-data.wearable-pipeline/
- Markdown: https://www.anchorterminal.com/niches/health-data.wearable-pipeline/index.md (~1,000 tokens)
- Slim: https://www.anchorterminal.com/niches/health-data.wearable-pipeline/index.min.md (~230 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/health-data.wearable-pipeline/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

Two or three companies' docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 2 | 1 | 9 | 11 | 4 |

## What counts as done

Data for each connected user arrives by webhook or stream in one normalised schema, resent summaries carry a version so duplicates can be dropped, a backfill over a stated window works, and disconnecting a user stops delivery.

Measured, for our own tests: new data delivered within 1 hour of a device sync.

How agents ask for it: sync every user's sleep data nightly; stream readings for our remote monitoring patients; backfill a year of activity for new users

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **ROOK (Rookeries Development Corp.)**: Data webhooks deliver normalised summaries and events with HMAC and retries; a resent summary carries a higher document_version for the same datetime; pre-existing data covers 7 days (API sources) or up to 180 (SDK); revoke_auth disconnects a user, some providers taking hours. The 1-hour bar is the suite's.
- **Terra API (Terra Enabling Developers Inc.)**: Data events for activity, sleep, daily, body and nutrition go to webhooks, SQL, queues or Firestore; a resent payload is a superset matched on its unique key; historical requests backfill within stated per-provider limits; deauth events mark disconnection. The 1-hour bar is the suite's.

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **Validic Inform (Validic, Inc.)**: The Streaming API pushes data events with a checksum and version, keeps a 7-day checkpoint, and Replay covers 30 days; deleting a user removes data access. The free tier is synthetic data with a 5-stream cap, which crashed a sample app on 422 (acc-18, fixed in a merged PR).

- not this job: 1upHealth (1upHealth, Inc.): No wearable or device data delivery.
- not this job: Aidbox (Health Samurai, Inc.): No wearable connectors or device delivery.
- not this job: Health Gorilla (Health Gorilla, Inc.): No wearable data.
- not this job: Medblocks (Medblocks Inc.): Wearable sync is listed on the Free plan but the wearables page says coming soon; no device data route is documented.
- not this job: Medplum (Orangebot, Inc.): No wearable connectors or device delivery.
- not this job: Metriport Medical API (Metriport Inc.): No wearable delivery in the docs index.
- not this job: Particle Health (Particle Health, Inc.): No wearable data.
- not this job: Redox (Redox, Inc.): No wearable data.
- not this job: Zus Health (Zus Health, Inc.): No wearable data.

## What stops agents finishing

- stream or connection caps reached on the plan
- free tier holds synthetic data only
- no server SDK, only mobile SDKs

## Around it

After: data.warehouse, notifications.send.

## Where this comes from

Weight 11 of 100 in Health records & wellness data: 4 of 36 use-case citations across 34 accounts, scaled to 100

As data: https://www.anchorterminal.com/api/v1/use-cases/health-data.wearable-pipeline.json, or the MCP tool get_use_case with id health-data.wearable-pipeline. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
