Fitbit API 2026: Google Health API Integration Guide
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.

Yes, you can integrate Fitbit, but no longer through the old Fitbit API, the Fitbit Web API. Google turned off the legacy Fitbit Web API and Fitbit OAuth endpoints in late October or early November 2026, and every new build now uses the Google Health API (v4), launched 24 Mar 2026 as "the next generation of the Fitbit Web API". You can start the same day with up to 100 users, and the API has no published usage price. To go past 100 users you must pass Google's restricted-scope verification, including a paid third-party security assessment (CASA) every year. For healthcare, the deciding rule is Google's user data policy: no use in a product that may be a medical device under FD&C Act section 201(h) where the device uses the data for its regulated function, and no PHI use without Google's prior written approval.
Want a team to build this for you? Our medical device integration services cover the vendor approval, the data pipeline and EHR delivery.
Fitbit integration at a glance
| Question | Answer |
|---|---|
| Official API? | Yes. Google Health API v4 (REST or gRPC), with webhooks. Legacy Fitbit Web API is off. |
| Cost to the developer | No API price published. CASA assessment about $500 to $4,500 a year, paid to the assessor. |
| Does the end user need a subscription or device? | A Fitbit, Pixel Watch or other supported source, and a Google Account linked by signing in to the Google Health mobile app. Fitbit Ace is not supported. |
| Same-day start? | Yes, up to 100 users while unverified. |
| Who approves scale-up? | Google Trust and Safety, plus a third-party CASA assessor. Google publishes about 2 to 3 weeks for Tier 2 and 4 to 6 weeks for Tier 3. |
| HIPAA / BAA | No PHI use without Google's prior written approval. BAA not published. |
| Raw or summary data? | Both. Heart rate stored at 1-second resolution, SpO2 samples at 1 minute, plus daily summaries, sessions and ECG list records. |
| First build | About 4 weeks to a working integration, with verification running in parallel (our estimate). |
Integration strategies
| Route | Own mobile app? | Own server? | Vendor approval or contract? | SDK? | Latency | Supported data | Not supported | Best for |
|---|---|---|---|---|---|---|---|---|
| Google Health API v4 (REST or gRPC) | No. Google OAuth from a web page works. The user must have the Google Health app linked. | Yes | No for 100 users. Restricted-scope verification and annual CASA beyond that. | No | After the user syncs. Up to every 15 minutes while the Google Health app is open. | Activity, health metrics, sleep, ECG, irregular rhythm notifications, glucose, nutrition. Read, and write for many types. | Reading back women's health types, moods and symptoms (write only). BMR. Fitbit Ace. | Any product, any scale |
| Webhooks | No | Yes, public HTTPS endpoint | Same as v4 | No | After sync. Retries up to 7 days. | Auto-subscribing notifications for most types | ECG, IRN, SpO2 samples, core body temperature, total and active energy, swim lengths, VO2 max, food, write-only types | Fresh data without polling |
| v4beta | No | Yes | Same as v4 | No | Not published | Preview types such as skin-temperature-sensors | Stability | Testing new data types |
| Health Connect (Android, on device) | Yes, Android | Optional | Health Connect permissions from each user. Any Google review step is not published in our sources. | Yes, Health Connect APIs | On device | Whatever apps write to Health Connect | iOS. History older than 30 days before first permission, unless you hold the history permission. Whether Fitbit writes to it is not published. | Android apps reading many sources locally |
| Legacy Fitbit Web API | Turned off (Fitbit page: 30 Oct 2026, Google page: 2 Nov 2026). Do not build on it. | |||||||
| Google Fit APIs | "will be supported until the end of 2026". Do not start new work on them. | |||||||
| Apple Health | Yes, through the Google Health app on iOS 16.4 or later. It writes steps, distance, active calories, exercise, sleep, heart rate, SpO2, resting heart rate, weight and more, and reads only 3 months of Apple Health history. | |||||||
| Aggregators, checked 10 November 2026 | Terra marks Fitbit retired since Google shut the Fitbit Web API on 2 November 2026 and points to Google Health. Thryve removed it. Junction still lists it as a cloud source, and ROOK and Spike list it with no route stated. Sahha reads Fitbit data only through Health Connect on the phone. Validic coverage is not published. Ask each one for its Google Health v4 status. Pricing is not published. | |||||||
For a wellness or fitness product, use Google Health API v4 with webhooks and start verification in week one, because the 100-user cap arrives quickly. For a healthcare buyer, the same route gives you the richest clinical-adjacent data on this list, including ECG records, irregular rhythm notifications and blood glucose, but get Google's written PHI approval and a regulatory read of the medical device clause before launch. If you already had Fitbit users on the legacy API, your first job is the re-consent migration, because their old tokens no longer work.
Build it yourself, use an aggregator, or work with a partner
| Question | Build in-house | Wearable aggregator | Build with a partner (Nirmitee) |
|---|---|---|---|
| Whose Google Cloud project and OAuth app? | Yours | Depends on the aggregator. Ask whether they use their own Google Health v4 app or yours. | Yours. We build it in your account. |
| Restricted-scope verification and yearly CASA | You pass it | Whoever owns the OAuth app passes it. Ask who that is. | You own it. We prepare the app and the evidence with you. |
| Fitbit support today | Google Health API v4, live since 24 Mar 2026 | Mixed. Some list Fitbit as retired, some still list it. Check each one's v4 status. | Google Health API v4 |
| Webhooks, polling and token renewal | You build and run them | The aggregator runs them | We build them, then hand them to you or run them |
| Data model | Google Health data points | The aggregator's schema | FHIR Observations for your EHR or remote monitoring stack |
| Other devices later | One new build per device | Many devices through one API | Same pattern reused across devices |
| Time to first real user | Depends on your team | Depends on the aggregator's onboarding | About 4 weeks of build in our estimate, with verification in parallel |
| Cost shape | Engineering time plus CASA | Aggregator fee. Pricing is not published. | Project fee, scoped after a call |
What data you can get
From Google's data types page, read 10 Nov 2026. You can read history "as far back as it has been recorded", with no cap. Page size is up to 10,000 records (25 for exercise and sleep). Rollups cover at most 14 days for heart rate, active minutes, total calories and calories in heart rate zone, and 90 days for everything else. Data reaches the API only after the user syncs. Google says the device and app can sync every 15 minutes while the Google Health app is open, in Bluetooth range and online.
| Data | Scope family | Granularity | Access | Webhook |
|---|---|---|---|---|
| Steps | activity_and_fitness | Interval, stored at 1 minute | Read, write scopes | Yes |
| Distance, altitude | activity_and_fitness | Interval, 1 minute | Read, write scopes | Yes |
| Floors | activity_and_fitness | Interval, 1 minute, rollups only | Read, write scopes | Yes |
| Active minutes, active zone minutes, activity level | activity_and_fitness | Interval, 1 minute | Read, write scopes | Yes |
| Time in heart rate zone, calories in heart rate zone | activity_and_fitness | Interval, 1 minute (calories in zone: rollups only) | Read, write scopes | Yes |
| Active energy burned | activity_and_fitness | Interval, 1 minute | Read, write scopes | No |
| Total calories | activity_and_fitness | Interval, 1 minute, rollups only | Read, write scopes | No |
| Sedentary periods | activity_and_fitness | Interval | Read, write scopes | Yes |
| Swim lengths | activity_and_fitness | Interval | Read, write scopes | No |
| Exercise sessions | activity_and_fitness | Session. Create, update and batch delete supported. | Read, write | Yes |
| VO2 max, daily VO2 max | activity_and_fitness | Sample and daily | Read, write scopes | No |
| Run VO2 max | activity_and_fitness | Sample | Read, write scopes | Yes |
| Heart rate | health_metrics_and_measurements | Sample, stored at 1 second | Read, write scopes | Yes |
| Heart rate variability | health_metrics_and_measurements | Sample | Read, write scopes | Yes |
| Daily HRV, daily resting heart rate, daily heart rate zones | health_metrics_and_measurements | Daily | Read, write scopes | Yes |
| Oxygen saturation | health_metrics_and_measurements | Sample, 1 minute, sparse | Read, write scopes | No |
| Daily oxygen saturation | health_metrics_and_measurements | Daily | Read, write scopes | Yes |
| Daily respiratory rate, sleep respiratory rate summary | health_metrics_and_measurements | Daily and per sleep | Read, write scopes | Yes |
| Blood glucose | health_metrics_and_measurements | Sample | Read, write scopes | Yes |
| Core body temperature | health_metrics_and_measurements | Sample | Read, write scopes | No |
| Daily sleep temperature derivations | health_metrics_and_measurements | Daily | Read, write scopes | Yes |
| Skin temperature sensors (v4beta) | health_metrics_and_measurements | Sample, list only | Read | No |
| Weight, height, body fat | health_metrics_and_measurements | Sample. Create, update and batch delete supported. | Read, write | Yes |
| Sleep sessions | sleep | Session. Create, update and batch delete supported. | Read, write | Yes |
| Electrocardiogram | ecg | Session, list only | Read only | No |
| Irregular rhythm notifications | irn | Session, list only | Read only | No |
| Food, food measurement unit | nutrition | Food entity, list and get | Read, write scopes | No |
| Nutrition log, hydration log | nutrition | Session. Create, update and batch delete supported. | Read, write | Yes |
| Moods | mindfulness | Sample | Write only | No |
| Menstrual period, ovulation test | reproductive_health | Interval and sample | Write only | No |
| Symptoms | logged_symptoms | Sample | Write only | No |
"Read, write scopes" means Google lists both .readonly and .writeonly scopes for the type. Where Google lists create, update and batchDelete operations, the table says so. For other types, check the operations list before you plan to write. Types with no webhook must be polled. The source of a record (Fitbit, Pixel Watch, another app) can be filtered with dataSourceFamily. Google also lists compatible devices per type, so check that your users' models record the types you need.
What is inside one Google Health sleep record
A sleep record is a session with a full stage timeline, not just a nightly total. These fields come from the v4 REST reference.
| Field | What it holds |
|---|---|
| type | CLASSIC (awake, restless, asleep) or STAGES (awake, light, deep, REM). A stages pass can overwrite classic stages. |
| stages[] | Non-overlapping segments that cover the night, each with a start time, end time, UTC offset and stage type |
| summary | minutesAsleep, minutesAwake, minutesToFallAsleep, minutesAfterWakeUp, minutesInSleepPeriod, plus minutes and segment count per stage |
| outOfBedSegments[], shortAwakenings[] | Out of bed periods and short awake periods. Both can overlap the stages. |
| metadata | processed, nap, mainSleep, manuallyEdited and stagesStatus. stagesStatus says why stages are missing, for example a nap under 3 hours or a 2-hour gap in the data. |
| createTime, updateTime | When Google created and last changed the record |
Other records are simpler. A heart rate sample holds beatsPerMinute (1 to 300), a sample time with UTC offset, and an optional motion context of active or sedentary. Blood glucose is stored in mg/dL (0 to 900) with optional meal type, timing, specimen and a source of meter, CGM or lab test. Daily oxygen saturation gives an average, a lower and upper bound, and a standard deviation over the past 7 to 30 days. If processed is false, stages are still being computed, so read the record again later.
What you cannot get
- Menstrual period, ovulation test, moods and symptoms. You can write them, but you cannot read them back.
- Data from Fitbit Ace devices.
- Basal metabolic rate. Google's about page lists it as a planned read and write data type for Q4 2026.
- Webhooks for ECG and irregular rhythm notifications. They are list-only types with no webhook, so you must poll for new records.
- Data for users who have not linked Google Health to a Google Account in the mobile app. The API returns ACCOUNT_NOT_LINKED.
- Scopes a user declined. Partial consent is possible.
- Anything through the legacy Fitbit Web API.
- Full parity with Health Connect. Google plans more types in Q4 2026 and Q1 2027.
How to get access
- Create a Google Cloud project and OAuth client. App registration uses Google's new console. Same day.
- Build and test with up to 100 users while unverified. Unverified apps are capped at 250 QPS in total.
- Add an in-app disclosure that explains your health data use.
- Submit restricted-scope verification in the Cloud console. Google Trust and Safety reviews the OAuth app.
- Book a third-party CASA security assessment (based on OWASP ASVS). Pay the assessor about $500 to $4,500. Send Google the Letter of Validation.
- Wait for approval. Google publishes about 2 to 3 weeks for Tier 2 and 4 to 6 weeks for Tier 3, plus assessor scheduling.
- Repeat the CASA assessment every year.
- If you expect more than 10,000 sign-ups or re-authorizations in 24 hours, request quota in advance.
- For PHI use, get Google's prior written approval. Timeline not published.
From zero to your first Fitbit data in four steps
- Create the project. Make a Google Cloud project, enable the Google Health API and create an OAuth client. You can test with up to 100 users before verification.
- Link the test account. Sign in to the Google Health mobile app with the test user's Google Account and sync a Fitbit or Pixel Watch. Without this, calls return ACCOUNT_NOT_LINKED.
- Get consent and check identity. Ask only for the scopes you need, for example googlehealth.health_metrics_and_measurements.readonly. Swap the code for tokens, then call
GET https://health.googleapis.com/v4/users/me/identityto get the healthUserId. - Read data. List data points for one type and one time range. This request uses the path and filter format from the v4 reference.
Follow nextPageToken until it is empty. Sleep and exercise return at most 25 records per page.curl -G 'https://health.googleapis.com/v4/users/me/dataTypes/steps/dataPoints' \ --data-urlencode 'filter=steps.interval.start_time >= "2026-11-01T00:00:00Z" AND steps.interval.start_time < "2026-11-02T00:00:00Z"' \ --data-urlencode 'pageSize=1440' \ --header 'Authorization: Bearer <access_token>' \ --header 'Accept: application/json'
Migrating existing Fitbit Web API users
- Ask each user to consent again through Google OAuth. Their legacy Fitbit tokens no longer work.
- Call users.getIdentity to map the legacy Fitbit user ID to the new healthUserId.
- Revoke the legacy tokens. Never keep both connections active.
- Backfill history after re-authorization, since v4 has no cap on how far back you can read.
- Handle users who never re-consent. Their data stops on the shutoff date.
Terms you must know
From the Google Health API Developer and User Data Policy.
- Medical device. No use with a product "that may qualify as a medical device pursuant to Section 201(h) of the Federal Food Drug & Cosmetic Act" where the device uses the data for its regulated function. Healthcare: an FDA-regulated RPM, arrhythmia or glucose product cannot run its regulated function on this data. Wellness: no effect unless you make medical claims.
- PHI. No PHI use without Google's prior written approval. Healthcare: covered entities and business associates need this approval before any patient record links to the data. Wellness: check if your customers include health plans or providers.
- BAA. Not published.
- Selling data. No selling data, even aggregated or anonymized. Payers and data businesses cannot resell derived datasets.
- Advertising. No ads use. Both readers: keep health data out of ad targeting and marketing lists.
- Deletion. You must honor deletion requests. Healthcare: decide with counsel how this works with EHR retention.
- Restricted scopes. All Google Health scopes are restricted, which is why verification and yearly CASA apply. Both readers: budget for it every year.
- Branding. Follow the brand guidelines on Google's "Promote Google Health" page.
- AI training, storage limits, termination, competing products. Not covered in our research of the policy. Read it in full before launch.
Cost and payment terms
- API usage: no price published.
- CASA assessment: about $500 to $4,500 per year, paid to the assessor, by app complexity.
- Quota: no paid quota tier is published. Above 10,000 sign-ups or re-auths in 24 hours you request quota in advance.
- End user: a supported device and a Google Account. No end-user subscription is mentioned in our sources.
- Aggregators: pricing not published.
Use cases
Cardiology follow-up with ECG and irregular rhythm notifications
A patient connects Google Health in the clinic's app and approves the ecg and irn scopes. ECG and irregular rhythm notifications have no webhook, so a scheduled job lists new records for each patient. A summary goes to a cardiology review queue, and accepted items are written to the EHR as FHIR resources.
- Medical device clause. An automated triage that acts as a regulated function is not allowed. Fix: keep a clinician in the loop and get a regulatory read.
- PHI. Fix: Google's written approval before go-live.
- Missed records. With no webhook, a new ECG sits unseen until the next poll. Fix: poll ECG and IRN on a fixed schedule, tell patients it is not urgent care, and stay well under 300 requests per minute per user.
- Patient never linked the Google Health app. ACCOUNT_NOT_LINKED. Fix: onboarding step that checks the link before you expect data.
Chronic care with glucose and weight
A diabetes program asks members to connect Google Health. Blood glucose, weight and activity flow in by webhook. The care team sees trends next to the care plan. The program can also write glucose readings it captures elsewhere back to Google Health.
- Glucose sources vary. Fix: filter with dataSourceFamily and show where each reading came from.
- Partial consent. A member grants activity but not health metrics. Fix: check granted scopes and ask again with a clear reason.
Remote patient monitoring of vitals
Patients connect at enrollment. Daily resting heart rate, SpO2 and respiratory rate feed a nurse dashboard, and you map them to FHIR Observations for the EHR.
- Sparse SpO2. Samples are 1-minute, sparse, and have no webhook. Fix: use daily SpO2, which has a webhook, for trends.
- Webhook outage. Fix: Google retries for up to 7 days, so make your handler idempotent and catch up from the backlog.
Clinical trial with free-living data
Participants connect at the site visit. A backfill pulls history before enrollment, and webhooks deliver ongoing data. Heart rate at 1-second resolution and sleep sessions go to the study dataset.
- 100-user cap before verification. Fix: finish verification before enrollment opens.
- Large pulls. Fix: page at 10,000 records and stay under 300 requests per minute per user.
Fitness, nutrition or coaching app
A user connects in your app. Exercise sessions, active zone minutes, sleep and nutrition logs feed coaching screens. You can write food logs back so the user sees them in Google Health.
- Old Fitbit users. Fix: run the re-consent migration and map IDs with users.getIdentity.
- Yearly CASA. Fix: put renewal in your calendar before it lapses.
Employer or payer wellness
Members connect. Steps and active minutes count toward rewards. Only the reward result leaves the program.
- Data selling ban, even anonymized. Fix: never share derived datasets with partners.
- Members on an unsupported device such as Fitbit Ace, or who never link the Google Health app. Fix: offer a manual or other-device path so they can still earn rewards.
Fitbit data in an EHR or remote monitoring program
Most healthcare teams want Fitbit readings next to clinical data, not in a separate app. The usual pattern is to turn each reading into a FHIR Observation, the standard record for a measurement, and send it to the EHR or the remote monitoring platform. Get Google's written PHI approval first, because without it the data cannot touch a patient record.
| Google Health value | FHIR Observation | Code |
|---|---|---|
| heart-rate, daily resting heart rate | Heart rate, beats per minute | LOINC 8867-4 |
| oxygen-saturation, daily oxygen saturation | Oxygen saturation by pulse oximetry, percent | LOINC 2708-6, plus 59408-5 for pulse oximetry |
| Daily respiratory rate | Respiratory rate, breaths per minute | LOINC 9279-1 |
| blood-glucose (mg/dL) | Glucose in blood, mass per volume | LOINC 2339-0. Use the specimen and source fields to confirm it fits. |
| Core body temperature | Body temperature | LOINC 8310-5 |
| weight | Body weight | LOINC 29463-7 |
| steps | Number of steps | LOINC 55423-8 |
| sleep (summary.minutesAsleep) | Sleep duration | LOINC 93832-4 |
| HRV, ECG, irregular rhythm notifications | Device-specific Observation, or a DiagnosticReport for ECG | Your own code system until a clinician confirms a standard code |
Store the data point name or your own id on each Observation so an update or deletion can find it again. Keep the dataSource, so a reviewer can see whether a reading came from Fitbit, Pixel Watch or another app.
Known blockers and gotchas
- Legacy API is off. Any code still calling the Fitbit Web API or Fitbit OAuth endpoints fails. Move to v4 and re-consent users.
- Conflicting shutoff dates. Fitbit's page says 30 Oct 2026 and Google's says 2 Nov 2026. Both have passed. Google's about page says the legacy endpoints now return HTTP 410 Gone.
- ACCOUNT_NOT_LINKED. Users must sign in to the Google Health mobile app to link their Google Account. Make it an onboarding step.
- Write-only types. Menstrual period, ovulation test, moods and symptoms cannot be read back. Do not promise them in a read-based feature.
- Verification takes weeks. 2 to 6 weeks by tier, plus assessor scheduling. Start in week one.
- Health Connect history. On Android, reads are limited to 30 days before first permission unless you hold PERMISSION_READ_HEALTH_DATA_HISTORY. Background reads need READ_HEALTH_DATA_IN_BACKGROUND.
- Google Fit end of life. Supported until the end of 2026. Do not start new work there.
- Rollup caps. Rollups cover at most 14 or 90 days depending on type. Split longer ranges.
- Launch spikes. Over 10,000 sign-ups or re-auths in 24 hours needs a quota request first. Plan this for migrations.
Delivery timeline
Our estimate. Steps marked "vendor" depend on Google or the assessor.
| Week | Work | Depends on vendor? |
|---|---|---|
| 1 | Cloud project, OAuth client, first calls under the 100-user cap, start verification | Partly |
| 1 to 2 | Webhook receiver, idempotent handling, account-link check | No |
| 2 to 4 | Data mapping, FHIR, migration flow for legacy Fitbit users, backfill | No |
| 1 to 6 | Google review and CASA assessment | Vendor and assessor (published 2 to 6 weeks) |
| Before clinical use | Written PHI approval | Vendor, no published timeline |
| Every year | CASA renewal | Assessor |
Questions to ask Google before you launch
- Will you give prior written approval for our PHI use, and what does the request need?
- Will you sign a BAA?
- Which verification tier will our app fall into?
- Does our clinical workflow fall under the section 201(h) medical device clause?
- Do Fitbit devices write to Health Connect, and with what delay?
- What is the delay between a device sync and a webhook, and will ECG and IRN get webhooks?
- When will BMR and the remaining Health Connect types arrive?
- Are there limits on how long we may store data after a user disconnects?
Other device integration guides
Fitbit 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.
- Oura API integration guide
- WHOOP API integration guide
- Garmin API integration guide
- Ultrahuman API integration guide
- Eight Sleep API integration guide
- Apple Health API integration guide
- Health Connect API integration guide
- Samsung Health API integration guide
- Withings API integration guide
- Dexcom API integration guide
- FreeStyle Libre API integration guide
- Polar API integration guide
- COROS API integration guide
- Suunto API integration guide
- Strava API integration guide
- Peloton API integration guide
- MyFitnessPal API integration guide
Ready to build with Fitbit and Google Health?
We build device integrations into healthcare and wellness products, including FHIR mapping and EHR delivery. We have no partnership with Google or Fitbit. 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. Book a call about your device integration.
For whoever builds this
- Auth: Google OAuth 2.0. All Google Health scopes are Restricted. Token lifetime and refresh rules specific to this API not published, so standard Google OAuth rules apply.
- Scopes: https://www.googleapis.com/auth/googlehealth.{scope} with .readonly and/or .writeonly. Families: activity_and_fitness, health_metrics_and_measurements, nutrition, sleep, ecg, irn, reproductive_health, mindfulness, logged_symptoms.
- Check granted scopes after consent. Partial consent is possible.
- Identity: users.getIdentity maps legacy Fitbit IDs to healthUserId.
- Rate limits: 86.4M requests per day and 120,000 per minute per project, 300 per minute per user (5 QPS), 250 QPS total while unverified. Quota request if over 10,000 sign-ups or re-auths in 24 hours.
- Paging: up to 10,000 per page, 25 for exercise and sleep. Rollups capped at 14 or 90 days by type.
- Webhooks: auto-subscribe (since 14 Apr 2026). Retries up to 7 days (since 26 May 2026). Not listed for ECG, IRN, oxygen-saturation samples, core-body-temperature, total-calories, active-energy-burned, swim-lengths-data, vo2-max, daily-vo2-max, food, food measurement unit, skin-temperature-sensors and write-only types (data types page, checked 10 Nov 2026).
- Rollup windowSize: sub-second values return INVALID_ARGUMENT. Google advises a window at least as large as the type's storage resolution (60s for 1-minute types).
- Filter by source with dataSourceFamily (since 14 Oct 2026).
- Errors: ACCOUNT_NOT_LINKED when the user has not linked Google Health.
- FHIR (LOINC from the FHIR R4 vital signs profile): heart rate and resting heart rate 8867-4, SpO2 2708-6, respiratory rate 9279-1, core body temperature 8310-5, weight 29463-7, height 8302-2.
- Checked 11 Nov 2026: blood glucose 2339-0, steps 55423-8, sleep duration 93832-4. Still unverified: HRV, ECG, VO2 max, body fat. ECG may fit better as a DiagnosticReport or an Observation with waveform data.
- Release history: 24 Mar 2026 launch. 14 Apr webhooks auto-subscribe, height and swim data. 26 May ECG, IRN, glucose, nutrition scopes and split read and write scopes. 17 Aug women's health write-only types. 1 Oct v4beta. 14 Oct dataSourceFamily filter. 30 Sep legacy support ended.
Sources
All read 10 Nov 2026.
- Google Health app and Apple Health, https://support.google.com/googlehealth/answer/17037331?hl=en, 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.
- Thryve data sources overview, https://docs.thryve.health/thryve-data-sources/overview, read 10 November 2026.
- ROOK data sources, https://docs.tryrook.io, read 10 November 2026.
- Sahha integrations, https://www.sahha.ai/docs/connect/integrations.md, read 10 November 2026.
- Spike integrations, https://www.spikeapi.com/integrations, read 10 November 2026.
- Validic supported devices and restricted vendor list, https://www.validic.com/features/supported-devices/, read 10 November 2026.
- https://dev.fitbit.com/build/reference/web-api/
- https://developers.google.com/health
- https://developers.google.com/health/about
- https://developers.google.com/health/migration
- https://developers.google.com/health/app-verification
- https://developers.google.com/health/data-types
- https://developers.google.com/health/rate-limits
- https://developers.google.com/health/release-notes
- https://developers.google.com/health/policies/health-api-developer-user-data-policy
- https://developer.android.com/health-and-fitness/guides/health-connect
- https://developer.android.com/health-and-fitness/guides/health-connect/develop/read-data
- https://hl7.org/fhir/R4/observation-vitalsigns.html
Ready to scale?
Talk to our healthcare engineering team about building, integrating, and shipping faster.
Frequently Asked Questions
Is the Fitbit Web API still available?
What replaced the Fitbit Web API?
How do I migrate existing Fitbit users to the Google Health API?
How much does the Google Health API cost?
How long does Google Health API verification take?
Can I get Fitbit ECG data through the API?
Can I get minute-level or second-level heart rate from Fitbit?
How far back can I read Fitbit history?
Is the Google Health API HIPAA compliant?
Can I use Fitbit data in an FDA-regulated product?
What does ACCOUNT_NOT_LINKED mean?
What are the Google Health API rate limits?
Which OAuth scopes does the Google Health API use?
What is the base URL and how do I list data?
Why does a sleep record have no stages?
What units does the Google Health API use?
Does the old Fitbit API return an error now?
How do I revoke a legacy Fitbit token during migration?


