Workouts data from every wearable, in one schema

What workouts looks like through one API

Workout data is where the cost of building your own integration layer shows up most concretely. Every provider has its own sport taxonomy, and they do not overlap cleanly: Strava uses PascalCase sport-type strings, Fitbit uses numeric activity IDs, WHOOP uses lowercase sport names, Garmin uses its own constants. There is no shared vocabulary and no published crosswalk.

WearLink maintains that crosswalk. 614 provider-specific sport identifiers are mapped into 90 unified workout types, per-provider, in code — so a "TrailRun" from Strava, activity ID 90009 from Fitbit and "running" from WHOOP all arrive as the same normalised type with the same field names. When a provider adds a sport, the mapping is updated once rather than in every downstream product.

Beyond the type, workouts carry duration, distance, energy, heart-rate summary and, where the device produces them, the running- and cycling-dynamics series: power, cadence, ground contact time, vertical oscillation, stroke count.

Where providers disagree

Webhook events for workouts

Summary: workout.created

Series streams:

• series.power.created
• series.speed.created
• series.cadence.created
• series.distance_walking_running.created
• series.distance_cycling.created
• series.distance_swimming.created
• series.running_power.created
• series.running_ground_contact_time.created
• series.running_vertical_oscillation.created
• series.swimming_stroke_count.created
• series.workout_effort_score.created

The full catalogue is in the event catalogue.