One API, many providers
Fitbit, Garmin, Oura, and more through a single normalized format. No per-provider integration work — just one schema for all health and fitness data.
Nexus
You build your product, we handle the wearable chaos.
Why Nexus
Section titled “Why Nexus”Data when and where you need it
Nexus sends your data when and where you need it so you don’t have to move a finger. Real-time webhooks, automatic retries, and dead-letter queues built in.
Provider-agnostic format
Every provider’s data normalized into one canonical schema. Compare heart rates, activities, and sleep across sources without writing transformation code.
Connect users in seconds
Drop-in OAuth flow handles tokens, refresh, and revocation. Your backend never touches provider credentials — just create a link and let your user approve.
Built for reliability
At-least-once delivery with automatic retries. Backfill historical data on demand. Deterministic IDs make deduplication trivial on your end.
You own the data shape
Every field is documented, typed, and predictable. null for missing data, never omitted. Version your integrations confidently with two-level schema versioning.
Streams at a Glance
Section titled “Streams at a Glance”Nexus organizes health and fitness data into five stream types based on how the data is produced and delivered.
| Stream | What it is | Example Types |
|---|---|---|
| Session | Bounded activities with a start and end | activity, sleep |
| Snapshot | Point-in-time measurements | body_measurement, blood_pressure, temperature |
| Timeseries | High-frequency sampled data in 15-minute chunks | heart_rate_series, location_series |
| Aggregate | Daily rollups | daily_summary |
| Profile | Slow-changing user metadata | user_profile |
Explore all 15 event types or jump straight to the event envelope format.