> For the complete documentation index, see [llms.txt](https://docs.tryterra.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tryterra.co/faq/help-topics/data-api-sdk/webhooks-dedup-and-sync-reliability/originating-source-via-device-data.md).

# Can a payload show its originating source through an aggregator?

It depends on the provider.

* **Apple Health:** the originating app is identifiable via `device_data.name` on the activity payload (for example `Polar Flow`). For daily/body/sleep, contributing sources appear across `device_data.name` and `device_data.other_devices` combined. Activity and sleep are keyed by HealthKit/source UUID as `summary_id`, so different sources never overwrite each other.
* **Health Connect (Android):** `device_data` is not currently populated for any data type, so a source coming through Health Connect is indistinguishable.
* **Withings:** `device_data.name` reflects the origin of each activity, which may be a connected third-party app (Google Fit, Samsung Health, HealthKit) rather than a physical Withings device, because Withings aggregates connected sources. `metadata.upload_type` value `6` indicates a third-party origin. Withings Body payloads don't currently carry `upload_type` or a populated device name.

See the [data models reference](https://docs.tryterra.co/reference/health-and-fitness-api/data-models) for the full payload structure.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.tryterra.co/faq/help-topics/data-api-sdk/webhooks-dedup-and-sync-reliability/originating-source-via-device-data.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.