Cloud Based Providers
| Primary Model | Providers |
|---|---|
| Hybrid | Fitbit, Withings, Oura |
| Push | Garmin, Strava, WHOOP, Cronometer |
| Polling | Wahoo, LibreView, Google Fit, Peloton, Zwift, EightSleep, Hammerhead, Dexcom |
Push
Push
In the Push model, the data provider proactively notifies Junction of any resource changes.Junction goes and fetches the notified resources, compare it against what we have already ingested, and send out the differences
(new or updated entities) to your Webhook endpoints or ETL Pipeline destinations.While resources using the Push model typically has lower latency than polling, data providers may impose throttling, debouncing
or batching semantics on these push notifications to Junction on their end.
Polling
Polling
Junction schedules a recurring job to query the data provider API resources:
- For most resources, the schedule is every 15 minutes or so.
- Some resources may use a sparser schedule due to data provider rate limits.
Hybrid
Hybrid
Some data providers support the Push model only on a subset of API resources.Junction prefers to use the Push model whenever available, but otherwise falls back to the Polling model.
SDK Based Providers
SDK Based Providers are all push-based, where data are pushed from the Junction SDK embedded inside your Android or iOS app.| Provider | Description |
|---|---|
| Apple HealthKit |
|
| Android Health Connect |
|
| Omron | Manual Post |
| Contour | Manual Post |
| Accu-Chek | Manual Post |