Skip to content

Cloud OAuth

Ultrahuman Ring API integration

Provider onboardingThe adapter is implemented; the production OAuth application is awaiting provider approval.OAuth application pending

Ultrahuman device illustration

Ultrahuman is the India-headquartered smart-ring maker and the provider most relevant to South Asian consumer health products, where its installed base is meaningful in a way it is not elsewhere.

Access is through a partner programme rather than open self-service registration, so the commercial conversation precedes the technical one. The data model is close to Oura's — sleep, recovery, HRV and temperature from a ring form factor.

For products serving Indian users, Ultrahuman plus Apple Health and Google Health Connect covers a large share of the actual device population, which is a different mix than a US-focused product would optimise for.

Connect a Ultrahuman user

Two calls. The first mints a hosted connect URL for your end-user; the second reads the normalised summaries once they have authorised with Ultrahuman. Subscribe a webhook to receive the same objects as they land.

connect + read — ultrahuman
# 1. Create a connect session for your end-user
#    The API key goes in X-WearLink-API-Key, not in Authorization.
curl -X POST https://wearlink.io/api/v1/connections/session \
  -H "X-WearLink-API-Key: $WEARLINK_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"user_id": "'"$USER_ID"'", "provider": "ultrahuman", "redirect_uri": "https://yourapp.com/connected"}'

# → { "connect_url": "https://wearlink.io/widget/connect?token=...", "expires_in": 3600 }
# Redirect the user there; they authorise ultrahuman and land back on your redirect_uri.
# The token is scoped to that one user — it is safe to put in a browser URL.

# 2. Pull normalised data whenever you want
curl -H "X-WearLink-API-Key: $WEARLINK_API_KEY" \
  "https://wearlink.io/api/v1/users/$USER_ID/summaries?provider=ultrahuman&days=7"

Ultrahuman data available through WearLink

  • Sleep
  • HRV
  • Resting heart rate
  • Steps
  • Skin temperature
  • SpO2
  • Recovery & movement index

Webhook events you can subscribe to

  • sleep.created
  • series.heart_rate_variability.created
  • steps.created
  • body_temperature.created

Normalised families this provider feeds: Sleep, Heart Rate Variability, Heart Rate, Steps & Daily Activity, Recovery & Readiness, Blood Glucose & CGM, Body & Skin Temperature.

What makes the Ultrahuman API hard to integrate directly

These are the things that turn an estimated one-week integration into a one-month one.

Partner access, not open registration

You cannot self-serve credentials the way you can with Fitbit or Strava. Expect a commercial conversation first.

Younger API surface

The partner API is newer than Oura's or Fitbit's and has changed more often. Pin your expectations and monitor for shape changes.

Ring sync latency

As with all rings, data arrives when the ring syncs to the phone app, not continuously.

FAQ

Ultrahuman API — frequently asked questions

How do I get Ultrahuman API access?
Through Ultrahuman's partner programme. It is not open self-service registration, so the timeline depends on their commercial review.
Is Ultrahuman relevant outside India?
It sells internationally, but its installed base is concentrated in India and the Gulf. For an India-focused product it is often the single most important ring provider.
How does Ultrahuman compare to Oura in the data model?
Very similar — sleep staging, HRV, resting heart rate, temperature and a composite recovery metric. Both normalise into the same WearLink schema, so switching or supporting both costs you nothing in application code.

Related

Other cloud integrations

Oura Ring API

Connectable now

The Oura Ring API (v2) is one of the cleaner wearable APIs to work with — the documentation is accurate and the daily-summary endpoints are stable. The complexity is not in reading it, it is in keeping it read: Oura backfills and revises data after the fact, so a sleep record you fetched this morning can legitimately change by this evening.

WHOOP API

Connectable now

WHOOP's developer API exposes the four objects the product is built around — cycles, recovery, sleep and workouts. The data is high quality and the model is coherent, which makes WHOOP a favourite for recovery and readiness products.

Fitbit API

Connectable now

Fitbit has the largest installed base of any dedicated wearable, which makes it the provider most consumer health products need first. It is also the API with the most historical baggage — the surface has accreted since 2011 and it shows in inconsistent date handling and endpoint shapes.

Strava API

Connectable now

Strava is the best-instrumented activity API in the consumer space and the only provider in the WearLink catalogue with a true push model — an activity upload triggers a webhook within seconds, not on a poll cycle. If your product cares about workouts rather than sleep or recovery, Strava is usually the fastest path to a working demo.

Withings API

Connectable now

Withings is the connected-scale and blood-pressure provider, which makes it the one that matters most for clinical-adjacent products — weight management, hypertension programmes, GLP-1 follow-up and remote patient monitoring. Its data is measurement-shaped rather than continuous: discrete readings taken when a user steps on a scale or straps on a cuff.

Garmin API

Provider onboarding

Garmin has the broadest data surface of any provider in the catalogue — if a metric exists in consumer wearables, a Garmin device probably measures it. For endurance, military, occupational-health and research use cases it is frequently non-negotiable.

Start with Ultrahuman — free for up to 3 users

No credit card. Your API key is issued at sign-up, and the hosted connect flow works from the first request.