Skip to content
WearLink

Product

IntegrationsData typesUse casesNutrition APIProvider statusSecurityPricing

Developers

DocumentationWebhook eventsAPI referenceSystem status

Resources

GuidesCompareAboutContact
Sign inStart free

Use case

Wearable API for Corporate Wellness Platforms

Steps, sleep and activity challenges across every device an employee brings, with per-user consent.

Start freeTalk to us
Corporate wellness

Wellness platforms are judged on participation, and participation depends on whether the employee’s own device is supported. A step challenge that works for Fitbit users and not for Garmin or Apple Watch users splits the office in half on day one.

WearLink connects the cloud providers and reads the phone stores through the mobile SDKs, then normalises steps, distance, active minutes and sleep into one daily object. Challenge logic is written once against that object.

Flat tiers keep the cost model simple for a per-seat product: a thousand employees on the Scale tier is one line item, regardless of how many of them sync ten times a day.

What usually goes wrong

Step counts are not comparable across devices

A wrist-worn tracker, a phone in a pocket and a ring count different things. Without provenance on every daily total, a leaderboard rewards the device rather than the activity.

Consent has to be individual and revocable

Employees must opt in per device and be able to withdraw. Managing that against six vendor OAuth implementations is a support burden.

Google Fit is deprecated

Android users are moving to Health Connect, which has no cloud API. Platforms that relied on Google Fit server-side need an on-device path.

How WearLink handles it

  • Daily activity object with provenance — Steps, distance, floors and active minutes arrive with the source provider and device type on every record.
  • Hosted connect and revoke — Employees connect through a hosted flow and can revoke at any time; the connection state is visible to you through the API.
  • Health Connect through the Kotlin SDK — The Android package reads Health Connect on the phone and pushes into the same pipeline as Fitbit or Garmin.
  • Seat-based flat pricing — Tiers are priced by connected end-users, not by sync volume, so the finance conversation is predictable.

FAQ

Corporate wellness — frequently asked

Can employees connect more than one device?
Yes. A single end-user record can hold several connections. Daily totals carry the source, so your challenge logic can pick one device per user or apply a merge rule.
How do we handle employees who leave?
Deleting the end-user through the API revokes every connection and removes stored data. Soft-deleted users return their seat to your plan.
Do you support Samsung Health?
Samsung Health is read on-device through the Kotlin SDK. There is no cloud API for it from any vendor.
What is the pricing for a 1,000-employee programme?
The Scale tier covers 1,000 end-users at a flat monthly price; Enterprise covers larger programmes with custom terms. See the pricing page for current figures.

Other use cases

Same API, different products

Fitness & coaching apps

Pull workouts, heart rate, recovery and sleep from the devices your members already wear.

Clinical & remote monitoring

Heart rate, blood pressure, glucose and sleep from consumer devices, in one auditable pipeline.

Insurance & incentive programmes

Verified activity and sleep data for behaviour-based incentives, with an audit trail behind every reward.

Research & digital biomarkers

High-resolution series from consumer wearables, with units and provenance you can cite.

Connect your first wearable today

Free for up to 3 connected users. No credit card. Your first API key is issued the moment you sign up.

Start freeRead the docs