An independent wearable data API, run by engineers

What we are building

One integration that turns 14 wearable and health-data sources into a single normalised schema, delivered by signed webhooks and a REST API. Today that means Oura, WHOOP, Fitbit, Strava, Withings through cloud OAuth, Apple Health, Google Health Connect and Samsung Health through the mobile SDKs, and 6 more providers in vendor onboarding.

On top of the pipeline sit the things a health product needs next: photo-based nutrition logging with a food database curated for South Asian dishes as well as Western ones, an energy-balance endpoint that fuses wearable burn with intake, health scores, and an audit log you can export.

How we make decisions

Provider status is derived, not typed. The homepage, the integrations hub and the provider page all read one content module that is reconciled against the running API. An earlier version of this site advertised three live providers for months after five were connectable; the fix was structural, not editorial.

Comparisons name where we lose. Terra has a far larger catalogue and compliance attestations we do not hold. The comparison pages say so, with dates and sources, because a customer who discovers a limitation after switching is one we lose anyway.

Pricing is flat. Tiers are priced by connected users, not by credits or sync volume, so the bill is knowable before launch.

We do not invent trust signals. There are no testimonials on this site because we do not yet have customers who have agreed to be named. When we do, they will be real and linkable.

Where we are

WearLink runs on isolated single-tenant infrastructure with Asia-Pacific (Malaysia) data residency; additional regions are available on Enterprise. The team works remotely. The fastest way to reach an engineer is hello@wearlink.io; sales, support and security all land in the same inbox and are answered by people who can change the code.