Historical Data Pull Range - Junction

Junction fetches the historical data immediately when the connection is established. The pull range can be estimated by [now - days_to_pull, now].

Provider	Default	Configurable	Remarks
Abbott LibreView	90 days	❌	-
Fitbit	90 days	⚠️	Activity and heartrate timeseries data are fixed to 14 days.
Garmin	90 days	✅	-
Google Fit	90 days	✅	-
Google Health API	90 days	✅	-
Oura	180 days	✅	-
Peloton	180 days	✅	-
Strava	14 days	✅	-
Wahoo	180 days	✅	-
WHOOP	180 days	✅	-
Zwift	270 days	✅	-
Withings	90 days	✅	-
8Sleep	90 days	✅	-
Apple HealthKit (SDK)	30 days	✅	On iOS 27 and later, the user’s HealthKit authorization window may limit how much historical data Junction can backfill.
Android Health Connect (SDK)	30 days	❌	Google restricts access to historical data to 30 days before the first successful permission request.
Hammerhead	30 days	✅	-
Dexcom	30 days	✅	-
Dexcom (G6 and older)	1 day	❌	-
MyFitnessPal	14 days	✅	-
Polar	28 days	❌	Polar only supports historical backfill for Sleep and Sleep Stream resources.
Cronometer	28 days	✅	-

The configurable maximum is 365 days at this time.

Customizing historical data pull range

Org Management API is available for the Scale plan.

You can configure the historical pull range using the Team Data Pull Preferences feature of the Org Management API. You can specify a number of days to backfill that uniformly applies to all resources of a provider, as well as overriding the number of days to backfill for specific resources.

The Team Data Pull Preferences you specified are advisory. There are scenarios in which Junction systems may not adhere strictly to your stated preferences.