> 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/sync-freshness-bottleneck-device-to-cloud.md).

# What sync frequency can I expect per provider?

Sync frequency depends on whether a provider is push-based or polled:

* **Push-based providers** (for example, Garmin) deliver whenever the user's device syncs, typically several times a day.
* **Polled providers** (for example, Oura) are fetched roughly every 15 minutes.

There's **no way to force higher frequency**, since the bottleneck is device-to-cloud sync. **Consuming webhooks as they arrive is the recommended architecture.**

For sleep specifically, Apple Watch, Garmin, Fitbit, and Oura do not stream intra-night. All deliver sleep only after the session finalises and the device syncs:

* Apple Watch as a post-wake batch via the iOS SDK.
* Garmin, Fitbit, and Oura via a ping-pull pattern.

None support real-time mid-sleep streaming. Separately, MyFitnessPal item-level food logs are supported and arrive in the `meals` array alongside aggregated macros.

See [receiving data updates](https://docs.tryterra.co/health-and-fitness-api/managing-user-health-data/receiving-data-updates) for the webhook flow.