Skip to content
WearLink

Product

IntegrationsData typesUse casesNutrition APIProvider statusSecurityPricing

Developers

DocumentationWebhook eventsAPI referenceSystem status

Resources

GuidesCompareAboutContact
Sign inStart free

Cloud OAuth

Eight Sleep API integration

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

Connect Eight Sleep freeSee the code
Eight Sleep device illustration

Eight Sleep measures sleep from the mattress rather than the wrist, which produces a genuinely different signal: no compliance problem, no charging gap, and thermal data no wearable can supply.

The important caveat is that Eight Sleep does not operate a formal public developer programme in the way Fitbit or Strava do. The integration runs against the client API, which means it is more exposed to unannounced change than a contractually supported partner API.

For sleep-focused and recovery products it is worth having, but treat it as a best-effort source rather than something to build a core guarantee on.

Connect a Eight Sleep 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 Eight Sleep. Subscribe a webhook to receive the same objects as they land.

connect + read — eight-sleep
# 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": "eight-sleep", "redirect_uri": "https://yourapp.com/connected"}'

# → { "connect_url": "https://wearlink.io/widget/connect?token=...", "expires_in": 3600 }
# Redirect the user there; they authorise eight-sleep 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=eight-sleep&days=7"

Eight Sleep data available through WearLink

  • Sleep stages
  • Bed & ambient temperature
  • HRV
  • Respiratory rate
  • Toss & turn events

Webhook events you can subscribe to

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

Normalised families this provider feeds: Sleep, Body & Skin Temperature, Respiratory Rate & SpO2.

What makes the Eight Sleep API hard to integrate directly

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

No formal public developer programme

There is no published contract or deprecation policy. The surface can change without notice.

Two sleepers, one bed

Dual-zone beds report per-side. Attributing the right side to the right user account is part of the integration, not an afterthought.

Presence, not wear

The device measures whoever is in the bed. A guest, a child or a pet changes what the data means.

FAQ

Eight Sleep API — frequently asked questions

Does Eight Sleep have an official API?
Not a formal public developer programme comparable to Fitbit or Strava. The integration works against the client API, which carries more change risk.
What does Eight Sleep add over a wrist wearable?
Bed and ambient temperature, and sleep measurement that does not depend on the user remembering to wear or charge anything.
Is it reliable enough for a production feature?
Treat it as a supplementary source. Because there is no supported contract, we would not recommend making it the single source of truth for a paid feature.

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 Eight Sleep — 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.

Start freeRead the docs