Device IntegrationHealthcare Interoperability

Eight Sleep API in 2026: How to Integrate Sleep Data

June 22, 202612 min read
Written by
Jitendra Choudhary
Jitendra Choudhary

CTO & Co-Founder

CTO & Co-Founder at Nirmitee.io. Architects healthcare integrations across FHIR, SMART on FHIR, ABDM and NHCX, writing from production experience taking hospital software from sandbox to go-live.

Eight Sleep API in 2026: How to Integrate Sleep Data

We could find no public Eight Sleep API for developers. There is no developer portal and no published partner program. You can still get Pod sleep data in two ways: through an aggregator such as Terra, which says it holds a partner relationship with Eight Sleep, or through Apple Health and Health Connect on the user's phone. Eight Sleep publishes no developer pricing, and aggregator fees apply. The rule that decides most projects: every route runs through a third party or the user's phone, so check that party's terms, BAA position and continuity before you design the product.

Want a team to build this for you? Our medical device integration services cover the vendor approval, the data pipeline and EHR delivery.

Eight Sleep integration at a glance

QuestionShort answer
Official API?No public API found. Terra says it uses "the Eight Sleep API, by way of the partner relationship Terra maintains". Not confirmed on an Eight Sleep page.
Cost to developer?Not published for Eight Sleep. Aggregator fees apply and are not published.
Does the end user need a subscription or device?An Eight Sleep Pod. Subscription needs for data sharing are not published.
Same-day start?Through Terra, yes per Terra: nothing to register with Eight Sleep. Through Apple Health, once your app exists.
Who approves scale-up?Your aggregator. A direct partnership path is not published.
HIPAA / BAA?Eight Sleep's privacy policy frames health data under Washington's My Health My Data Act and Nevada's health data law, not HIPAA. BAA not published.
Raw vs summary data?Nightly summaries plus a hypnogram via Terra. No raw sensor signals.
First build1 to 2 weeks via Terra, 2 to 3 weeks via Apple Health. Our estimate.

Integration strategies

RouteOwn mobile app?Own server?Vendor approval or contract?SDK?Data latencySupported dataNot supportedBest for
Public cloud REST APINot found in public docs. No Eight Sleep developer portal.
Partner API (direct)Not published. Terra reports a partner relationship. How another company gets one is not published.
Aggregator: TerraNoYes, to receive webhooksContract with Terra. Nothing to register with Eight Sleep, per TerraNo (Terra widget)Terra polls every 5 to 10 minutes after the Pod syncsSleep timing, stages, hypnogram, latency, efficiency, HR, HRV, respiratory rate, snoring, sleep scoreRaw signals, bed temperature controlFastest start for both readers
Aggregator: Vital / JunctionNoYesWith the aggregatorNoNot publishedLists Eight Sleep as a cloud source with password sign-in. Fields not publishedNot publishedTeams already on Junction
Apple Health / HealthKitYesOptionalNoHealthKitAfter phone syncSleep. Eight Sleep also reads steps and exercise for Biological AgeAnything beyond sleep is not publishediPhone apps that read HealthKit
Health ConnectYesOptionalNoHealth ConnectNot publishedListed as an integration by Eight Sleep. Fields and setup not publishedNot publishedTest before you plan on it
Webhooks from Eight SleepNone. Terra says Eight Sleep does not push to it.
Unofficial app endpoints (pyEight and similar)NoYesNo. Using them may break Eight Sleep termsNoUnknownUnknownUnknownNot recommended
User data exportNoYes, to receive filesNoNoManualA user reported only an emailed download linkOngoing syncOne-off research backfill

For a healthcare buyer in sleep medicine, RPM or behavioral health: start with Terra, because it needs no app and gives nightly HR, HRV and breathing rate. Confirm Terra's BAA position separately. For a consumer sleep or coaching app that already reads HealthKit or Health Connect: read Eight Sleep's data there first, then add Terra if you need the hypnogram or snoring.

Build it yourself, use an aggregator, or work with a partner

QuestionBuild in-house (Apple Health or Health Connect)Wearable aggregatorBuild with a partner (Nirmitee)
Whose agreement with Eight Sleep?None. The user shares data to the phone, and you read it there.The aggregator's. Eight Sleep publishes no developer program you can join.None of ours. We build on the route you pick.
Terms riskApple and Google rules for health data apply to your appYou depend on the aggregator's agreement continuingYour counsel reads it. We design storage around the answer.
Mobile app needed?YesNoDepends on the route
Data modelHealthKit or Health Connect typesThe aggregator's schemaFHIR Observations for your EHR or remote monitoring stack
Other devices laterMany devices write to the same phone storeMany devices through one APISame pattern reused across devices
Time to first real user2 to 3 weeks in our estimate (Delivery timeline below)1 to 2 weeks in our estimateSame as the Delivery timeline below
Cost shapeEngineering timeAggregator fee, not publishedProject fee, scoped after a call
Every way to get Eight Sleep data, and what each one needs.

What data you can get

Via Terra (third party description).

Data typeGranularityHistory windowPush or pull
Sleep session start and endPer nightNot publishedTerra webhook
Time in bed, asleep, awakePer nightNot publishedTerra webhook
Light, deep, REM totalsPer nightNot publishedTerra webhook
HypnogramStage timeline in the nightNot publishedTerra webhook
Sleep latency, efficiencyPer nightNot publishedTerra webhook
Average heart ratePer nightNot publishedTerra webhook
HRVPer nightNot publishedTerra webhook
Respiratory ratePer nightNot publishedTerra webhook
Snoring episodes and durationPer nightNot publishedTerra webhook
Sleep scorePer nightNot publishedTerra webhook

On Apple Health and Health Connect, which fields Eight Sleep writes is not published.

What is inside one Eight Sleep night

Eight Sleep's app terms list the sleep activity its devices collect. This is the richest record Eight Sleep itself describes.

MetricWhat Eight Sleep says it collects
TSTTotal sleep time
StagesTime and percent in deep, light and REM sleep
WASOWake after sleep onset
SOLSleep onset latency, the time it takes to fall asleep
HR, HRV, breath rateHeart rate, heart rate variability and breathing rate
SnoringSnoring

Sample rates, units and the HRV method are not published. On the phone, the stages land in standard shapes. HealthKit sleep analysis has the values inBed, awake, asleepCore, asleepDeep, asleepREM and asleepUnspecified. Health Connect sleep sessions carry stages such as awake, light, deep, REM and out of bed. Which of these Eight Sleep writes is not published, so test with a real Pod.

What you cannot get

  • A public Eight Sleep API or developer portal.
  • Raw sensor signals.
  • Bed temperature settings or control.
  • Push from Eight Sleep. Terra polls.
  • A published history window, rate limit or OAuth scope list.
  • SpO2: not in Terra's Eight Sleep field list, and not published for any other route.
  • Any FDA-cleared measurement. No clearance is confirmed. Press in August 2026 described seeking sleep apnea clearance as a future step.

How to get access

  1. Decide the route: Terra, Junction, or Apple Health and Health Connect.
  2. For Terra: sign a Terra contract. Terra says there is nothing to register with Eight Sleep.
  3. Embed Terra's connect widget. The user signs in on Eight Sleep's own page (per a search summary of Terra's page, not confirmed in our fetch).
  4. Set your webhook URL in Terra and pick JSON, FIT or FHIR output.
  5. For Apple Health or Health Connect: Eight Sleep's privacy policy lists these as integrations. The user must share Pod data there, then grant your app read access on the phone. The exact steps in the Eight Sleep app are not published.
  6. For a direct partnership with Eight Sleep: no public path. Contact Eight Sleep. Who approves and how long are not published.

From zero to your first Eight Sleep data in four steps

Eight Sleep has no developer request to show, so this uses the phone route, built only on Apple and Google docs.

  1. Have the user link the phone store. Eight Sleep's app terms let the user connect with Apple Health and authorize a link to a third-party app. Its privacy policy names Apple Health and Google Health Connect.
  2. Ask for read access to sleep only. On iPhone, request read access to the HealthKit sleep analysis type. On Android, declare android.permission.health.READ_SLEEP, plus READ_HEART_RATE or READ_RESPIRATORY_RATE if you test those.
  3. Read the sleep sessions. This is Health Connect's documented read pattern:
    val response = healthConnectClient.readRecords(
        ReadRecordsRequest(
            SleepSessionRecord::class,
            timeRangeFilter = TimeRangeFilter.between(startTime, endTime)
        )
    )
    for (session in response.records) {
        // session.stages holds each stage with its start and end time
    }
  4. Check the source, then map. Keep only records whose data origin is the Eight Sleep app, so a watch on the same wrist does not double count. Then map each night to FHIR as shown below.

Terms you must know

There are no public developer terms. The only Eight Sleep document in our research is its Consumer Health Data Privacy Policy.

  • Health data law: the policy covers health data under Washington's My Health My Data Act and Nevada's consumer health data law. For a healthcare product this tells you Eight Sleep treats itself as a consumer company, not a HIPAA entity. For a wellness product, expect users to read Eight Sleep data as covered by those state laws, so your own privacy notice should be as clear.
  • Third-party sharing: the policy lists Apple Health and Health Connect as third-party integrations. Once data reaches the phone, the phone platform's rules and your own app's terms apply.
  • BAA: not published. Ask Eight Sleep directly, and ask your aggregator whether it signs one.
  • Medical use: not published. With no FDA clearance confirmed, present Pod data as wellness data.
  • Storage and retention, AI training, branding, data selling, termination, competing products: not published for any developer route. Ask your aggregator what its Eight Sleep agreement allows.
  • Unofficial endpoints: we did not check terms. Unofficial app endpoints are not a supported route and can change without notice.

Cost and payment terms

  • Eight Sleep developer fee: not published.
  • Aggregator fees: apply, not published. Ask Terra or Junction for a quote.
  • End user: needs a Pod. Whether a membership is needed for data sharing is not published.

Use cases

One night of Pod sleep data, through Terra, to the clinician.

Sleep medicine follow-up

A patient with insomnia connects their Pod through Terra in your portal. After each night Terra polls, then posts the sleep summary to your webhook. You map sleep duration, latency and efficiency to FHIR and show a 30-night trend to the clinician. Data used: sleep timing, latency, efficiency, stages.

  • Pod did not sync, so nothing arrives. Fix: flag missing nights instead of treating them as no sleep.
  • Stage totals read as polysomnography. Fix: label them consumer device estimates.
  • Terra delay of 5 to 10 minutes after sync. Fix: run reports next morning, not at wake time.

Remote monitoring of nightly vitals

A heart failure or recovery program watches nightly heart rate, HRV and breathing rate. The patient connects the Pod once through Terra's widget. Each night Terra posts the summary to your webhook. You store it as FHIR Observations and alert the care team when a value moves outside the patient's own baseline. Data used: average HR, HRV, respiratory rate.

  • A partner shares the bed. How the Pod separates two sleepers is not published. Fix: ask Eight Sleep or Terra, and confirm with the patient at onboarding.
  • Pod data is not cleared for clinical use. Fix: use it for trend review, not diagnosis or billing claims.

Behavioral health program

A therapist sees sleep regularity next to mood check-ins. Users connect through Apple Health in your app. Data used: sleep duration and timing.

  • Fields Eight Sleep writes to HealthKit are not published. Fix: test with a real Pod before you promise a metric.
  • User denies one HealthKit permission. Fix: show which data is missing and how to grant it.

Trial with a sleep endpoint

Participants with Pods at home connect through Terra. Data lands as FHIR or JSON on your server. Data used: total sleep, efficiency, latency.

  • No contract with Eight Sleep itself. Fix: get Terra's written terms on data rights and continuity before first patient in.
  • Backfill limit unknown. Fix: connect at enrollment.

Sleep coaching app

Users connect the Pod through Terra in your app's settings. When the night's summary reaches your webhook, your server stores it and the app shows sleep score, snoring and HRV the next morning with one suggested change. Data used: sleep score, snoring, HRV.

  • Duplicate nights from two routes. Fix: pick one source per user.
  • Pod did not sync, so the morning screen is empty. Fix: show "waiting for last night" and refresh when the webhook lands.

Eight Sleep data in an EHR or remote monitoring program

Most healthcare teams want Pod readings next to clinical data. The usual pattern is to turn each nightly value into a FHIR Observation, the standard record for a measurement, and send it to the EHR or remote monitoring platform. Label every one as a consumer device reading, since no FDA clearance is confirmed.

Eight Sleep valueFHIR ObservationCode
Total sleep timeSleep durationLOINC 93832-4
Deep sleepDeep sleep durationLOINC 93831-6
Light sleepLight sleep durationLOINC 93830-8
REM sleepREM sleep durationLOINC 93829-0
Heart rateHeart rate, beats per minuteLOINC 8867-4
Breath rateRespiratory rate, breaths per minuteLOINC 9279-1
HRVHeart rate variabilityLOINC 80404-7 is the SDNN code. Eight Sleep does not publish its HRV method, so confirm it or use your own code.
Sleep score, snoring, WASO, SOLDevice-specific ObservationYour own code system

Store the source record id on each Observation, so a resync updates the same record instead of adding a new one.

Known blockers and gotchas

  • No public API. Your access depends on an aggregator's relationship with Eight Sleep. Ask what happens to your users if that ends.
  • Polling delay. Terra polls every 5 to 10 minutes. Eight Sleep does not push.
  • Unconfirmed claims. The partner relationship and the OAuth sign-in come from Terra, not from Eight Sleep pages.
  • Consumer health law, not HIPAA. Eight Sleep's policy points to Washington and Nevada health data laws.
  • No FDA clearance confirmed. Keep Pod data out of diagnostic claims.
  • Data export is thin. A user reported only an emailed download link.
  • Community libraries. pyEight and similar use unofficial endpoints. Do not ship on them.

Delivery timeline

Our estimate.

WeekWorkDepends on vendor?
1Terra contract and widget, webhook receiverYes, Terra
2FHIR mapping and test with a real PodNo
Alt: 2 to 3Apple Health or Health Connect route in your mobile appNo
UnknownDirect partnership with Eight SleepYes. Not published

Questions to ask before you sign

  1. To Eight Sleep: is there a partner API, and how does a healthcare company apply?
  2. To Eight Sleep: which fields do you write to Apple Health and Health Connect?
  3. To your aggregator: what does your agreement with Eight Sleep allow, and for how long?
  4. To your aggregator: will you sign a BAA?
  5. How much history can we pull when a user first connects?
  6. Does the user need an Eight Sleep membership for data sharing?
  7. Will SpO2 or raw signals ever be offered?

Other device integration guides

Eight Sleep is often one device among several. Each guide below uses the same layout, so you can compare access, data and terms side by side. For the full service, see medical device integration.

Ready to build with Eight Sleep data?

Tell us your device, your users and your target date, and we will send back the route, the vendor approvals you need and a build plan. We do not have an existing Eight Sleep partnership. Book a call about your device integration.

For whoever builds this

  • No Eight Sleep endpoints, scopes or token rules are published.
  • Terra: manages Eight Sleep credentials, polls every 5 to 10 minutes, posts to your webhook. Output JSON, FIT or FHIR.
  • User sign-in: on Eight Sleep's own OAuth page via Terra (search summary, unconfirmed).
  • HealthKit and Health Connect: field list not published. Test on a device.
  • FHIR mapping (our mapping, verify): heart rate 8867-4, HRV 80404-7, respiratory rate 9279-1, sleep duration 93832-4, deep 93831-6, light 93830-8, REM 93829-0 (all codes checked in the LOINC search on 11 Nov 2026).
  • Versions and sunsets: not published.

Sources

All read 10 November 2026.

  • Eight Sleep help on other tracking apps, https://help.eightsleep.com/en_us/does-the-eight-sleep-app-sync-up-with-other-tracking-devices-rk25tVytP, read 10 November 2026.
  • Terra supported integrations, https://docs.tryterra.co/reference/health-and-fitness-api/supported-integrations, read 10 November 2026.
  • Junction providers list, https://docs.junction.com/wearables/providers/introduction, read 10 November 2026.
  • https://www.eightsleep.com/ca/legal/consumer-health-data-privacy-policy/
  • https://tryterra.co/blog/eight-sleep-integration-terra-api (third party, 7 October 2026)
  • https://tryterra.co/integrations/eightsleep (third party)
  • https://forum.intervals.icu/t/eight-sleep-integration/6316 (third party)
  • https://fortune.com/2026/08/24/eight-sleep-fda-tether-longevity-mattress-cover-pod-billionaires-zuckerberg-musk-healthcare-apnea-sleep/ (press)

Ready to scale?

Talk to our healthcare engineering team about building, integrating, and shipping faster.

Frequently Asked Questions

Does Eight Sleep have a public API?

We found no public API and no developer portal. Access comes through aggregators such as Terra, or through Apple Health and Health Connect.

How can I get Eight Sleep Pod data into my app?

Use an aggregator like Terra, which posts nightly sleep data to your webhook, or read what Eight Sleep writes to Apple Health or Health Connect from your mobile app.

What Eight Sleep data does Terra provide?

Per Terra: sleep timing, time in bed, asleep and awake, light, deep and REM totals, hypnogram, latency, efficiency, average heart rate, HRV, respiratory rate, snoring and sleep score.

Does Eight Sleep push data in real time?

No. Terra says Eight Sleep does not push to it and that Terra polls every 5 to 10 minutes after the Pod syncs.

Is Eight Sleep data covered by HIPAA?

Eight Sleep's privacy policy frames health data under Washington's My Health My Data Act and Nevada's health data law. It does not describe HIPAA coverage, and no BAA is published.

Is the Eight Sleep Pod FDA cleared?

We found no confirmed FDA clearance. Press in August 2026 described sleep apnea clearance as a future goal.

Can I control Pod temperature through an API?

No official route for this is published.

Can users export their Eight Sleep data?

One user reported only an emailed data download link. No regular export format is published.

Should I use unofficial Eight Sleep libraries like pyEight?

We do not recommend it. They rely on unofficial app endpoints that can change, and terms risk was not checked.

How long does an Eight Sleep integration take?

Our estimate is 1 to 2 weeks through Terra and 2 to 3 weeks through Apple Health with your own app. A direct partnership has no published timeline.

Which permissions does my app need to read Eight Sleep data on Android?

Health Connect needs android.permission.health.READ_SLEEP for sleep sessions. Add READ_HEART_RATE, READ_HEART_RATE_VARIABILITY or READ_RESPIRATORY_RATE only if you find Eight Sleep writes those types on a real device.

How much history can I read when a user first connects?

Eight Sleep does not publish a history limit for any route. On Health Connect, apps can read up to 30 days before the user first granted access. Older data needs the separate READ_HEALTH_DATA_HISTORY permission.

Which sleep stages show up in Apple Health?

HealthKit sleep analysis uses inBed, awake, asleepCore, asleepDeep, asleepREM and asleepUnspecified. Eight Sleep collects deep, light and REM time, but it does not publish which HealthKit values it writes. Test with a real Pod.

Does Eight Sleep send webhooks per data type?

No. Eight Sleep publishes no developer API and no webhooks. On the phone routes your app reads the store. Through an aggregator, the aggregator's own webhook delivers the night.

What units does Eight Sleep use for HRV and breath rate?

Not published. Its app terms name HR, HRV and breath rate but give no units or method. Check the values on a real Pod before you map them, and keep HRV on your own code until the method is known.

Is there an Eight Sleep API version or rate limit to plan for?

No version or rate limit is published, because there is no public API. Plan around the limits of the route you use: Health Connect, HealthKit or your aggregator.
Share