Dexcom API Integration Guide 2026: CGM Data Access
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, the Dexcom API lets you bring Dexcom glucose data into your product: the official route is Dexcom API v3. It is a cloud REST API with OAuth sign-in, and registration is free. Dexcom has not published any fees for production access. The rule that decides most projects is timing: US data arrives about 1 hour late, and you can serve only 5 real users until Dexcom approves your app for Full Access.
Want a team to build this for you? Our medical device integration services cover the vendor approval, the data pipeline and EHR delivery, and our remote patient monitoring software work covers RPM programs.
Dexcom integration at a glance
| Question | Short answer |
|---|---|
| Is there an official API? | Yes. Dexcom API v3, REST with OAuth 2.0, pull only. |
| Cost to the developer? | Registration is free. Fees for Limited or Full Access are not published. |
| What does the end user need? | A supported Dexcom CGM (G6, G7, G7 15-day) and a Dexcom account. Dexcom ONE and ONE+ are supported by the API but not sold in the US. Whether the user needs any paid Dexcom plan for API sharing is not published. |
| Same-day start? | Yes, with sandbox data. Real data needs a Limited Access approval. |
| Who approves scale-up? | Dexcom. The Strategic Partnerships team approves Limited Access. A technical and commercial review gates Full Access. No waiting time is published. |
| HIPAA and BAA? | Each user completes a HIPAA authorization during sign-in. Whether Dexcom signs a BAA with partners is not published. |
| Raw or summary data? | Individual glucose readings with trend, plus events, calibrations, alerts and devices. Delayed 1 hour in the US. |
| First build | About 3 weeks of engineering. Vendor approval time comes on top. Our estimate. |
Integration strategies
| Route | Own mobile app? | Own server? | Vendor approval or contract? | SDK? | Latency | Supported data | Not supported | Best for |
|---|---|---|---|---|---|---|---|---|
| Dexcom API v3 (cloud REST) | No. A web sign-in page works. | Yes | Yes. Free sandbox, then Limited Access (5 users) and Full Access review, plus a Data Licensing Agreement. | No | 1 hour US, 3 hours outside US | Glucose readings, events, calibrations, alerts, devices, data range | Real-time glucose, partial scopes, push | Most clinical and wellness products |
| Webhooks or push | Not published. All v3 endpoints are GET, so you poll. | |||||||
| Phone SDK | Not published on the developer site. | |||||||
| Partner or real-time API | Not published on the developer site. Ask Dexcom directly. | |||||||
| Apple Health or Health Connect | G7 and Stelo write glucose to Apple Health with a 3-hour delay. Stelo also writes glucose to Health Connect with a 3-hour delay. G7 to Health Connect is not published by Dexcom. Glucose is the only type written, so this route is not real time. | |||||||
| Aggregator (Junction) | No | Yes, to receive data from the aggregator | Contract with the aggregator. Dexcom approval terms through an aggregator are not published. | Aggregator SDK or API | At best the Dexcom delay | Junction documents a Dexcom v3 provider | Anything Dexcom v3 lacks | Teams already using Junction for other devices |
| Aggregators, checked 10 November 2026 | Terra and Thryve list Dexcom as a cloud API source. ROOK and Spike list it with no route stated. Validic lists Dexcom as restricted: you apply with Dexcom, US and EU, and the EU is closed. Sahha coverage is not published. Under whose Dexcom approval each one runs is not published. | |||||||
| File export | Not published on the developer site. | |||||||
For a clinical buyer, go direct to the Dexcom API v3. You need your own approval and Data Licensing Agreement anyway, and you keep control of the HIPAA authorization flow. For a wellness or coaching team that already pays for an aggregator, ask the aggregator whether its Dexcom access covers you, then compare that with a direct build of about 3 weeks.
Build it yourself, use an aggregator, or work with a partner
| Question | Build in-house | Wearable aggregator | Build with a partner (Nirmitee) |
|---|---|---|---|
| Whose Dexcom app and approval? | Yours | Depends on the aggregator. Validic says you apply with Dexcom yourself. For the others it is not published. | Yours. We build it in your account. |
| Data Licensing Agreement | You accept it and your counsel reads it | Not published whether the aggregator's agreement covers you | You accept it. We design storage and screens around it. |
| Polling and token rotation | You build and run them | The aggregator runs them | We build them, then hand them to you or run them |
| Data model | Dexcom's own fields | 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 3 weeks of build in our estimate, plus Dexcom approval time |
| Cost shape | Engineering time | Aggregator fee. Pricing for Dexcom on these platforms is not published. | Project fee, scoped after a call |
What data you can get
| Data type | Granularity | History | Push or pull |
|---|---|---|---|
| Estimated glucose values (egvs) | Each reading, in mg/dL, with trend rate in mg/dL/min | Not published. Use dataRange per user. Max 30 days per request. | Pull |
| Events | Each user-entered event | Same | Pull |
| Calibrations | Each fingerstick calibration | Same | Pull |
| Alerts | Each alert record | Same | Pull |
| Devices | Device records | Same | Pull |
| Data range | The span of data held for the user | Not limited to 30 days | Pull |
What is inside one Dexcom glucose record
Each record from the egvs endpoint holds more than a number. These fields come from Dexcom's v3 API reference.
| Field | What it holds |
|---|---|
| recordId | A unique id for the reading. Use it to avoid duplicates when windows overlap. |
| systemTime and displayTime | systemTime is UTC by the device clock. displayTime is the time shown to the user. Phone records carry a UTC offset, receiver records do not. |
| value | Glucose in mg/dL. 40 to 400 is the measuring range. 39 means below 40 and 401 means above 400. Neither is shown to the user as a number. |
| status | "low" or "high" when the value is outside the measuring range, otherwise null |
| trend and trendRate | The arrow, such as flat, singleUp or doubleDown, and the rate in mg/dL/min behind it |
| transmitterGeneration, displayDevice, displayApp | The sensor generation (for example g6 or g7), the display (receiver, iOS or android) and the app |
| transmitterId, transmitterTicks | A hashed transmitter id that cannot be matched to the real one, and seconds since the transmitter started |
Events add carbs in grams, insulin in units (fast or long acting), exercise in minutes, fingerstick glucose in mg/dL and health notes such as illness or stress. Each event has an eventStatus of created, updated or deleted, so your sync must handle edits. Dexcom ONE returns an empty events list. Alerts give the alert name (for example urgentLow, high or noReadings) and its state. Dexcom ONE+ does not support the Urgent Low, Urgent Low Soon, Rising Fast and Falling Fast alerts.
Supported devices and regions
| Item | What Dexcom publishes | What it means for you |
|---|---|---|
| G6, G7, G7 15-day | Supported by API v3 | These are the sensors your US users will have. |
| Dexcom ONE, ONE+ | Supported by API v3, not sold in the US | Only relevant if you also serve users outside the US. |
| US host | https://api.dexcom.com, 1-hour delay | Default for US programs. |
| EU and rest of world host | https://api.dexcom.eu, 3-hour delay | Store each user's region and call the matching host. |
| Japan host | https://api.dexcom.jp | Separate host. Plan for it only if you serve Japan. |
| Receiver uploads | Dexcom Uploader over USB, available immediately | Only USB receiver uploads are published as immediate. Plan on the 1 or 3 hour delay for everything else. |
What each user sees when they connect
The user signs in on a Dexcom page, sees the four scopes and completes a HIPAA authorization. The scopes are Estimated Blood Glucose Levels, Calibration Data, Events Entry Data and Device Details. The user approves all four or none. You cannot change this list. Write your own consent screen before the redirect so the user knows why you need each one. If the user declines, you get no code and no data, so show a clear way back into the flow.
What you cannot get
- Real-time glucose. US data is delayed 1 hour and data outside the US 3 hours. Receiver uploads through Dexcom Uploader over USB show up right away.
- A subset of data. Scopes are all or nothing. You cannot ask for glucose only, and users cannot approve only some scopes.
- Push notifications or webhooks. None are published.
- More than 30 days in one request. Longer windows return HTTP 400.
- Writing data back to Dexcom. Not published.
- A published history limit. Call dataRange for each user.
How to get access
- Register for free on developer.dexcom.com. You get apps, credentials, sandbox data and support requests. You can start the same day.
- Build against the sandbox at https://sandbox-api.dexcom.com.
- Apply for Limited Access from My Apps with "Apply for Upgrade". Commercial developers send a partnership request through the Dexcom Partnerships page. Researchers use the research portal. The Strategic Partnerships team decides. Waiting time is not published.
- If approved, accept the Data Licensing Agreement. Dexcom says it is non-negotiable. You can then test with up to 5 real users, each completing OAuth and the HIPAA authorization.
- Apply for Full Access (Digital Health Partner) with "Apply for Upgrade" and the Full Access Questionnaire. Dexcom runs a technical and commercial review per app and can ask you to fix implementation or screen issues. Waiting time is not published.
- Stay a partner. Publish at least one Full Access app, and keep at least one active Dexcom user connected within 60 days of public launch and at all times after.
From zero to your first Dexcom data in four steps
- Register an app. Sign up free on developer.dexcom.com, create an app in My Apps and register your redirect URI. Note the client ID and secret.
- Connect a sandbox user. Send the browser to https://sandbox-api.dexcom.com/v3/oauth2/login with client_id, redirect_uri, response_type=code and scope=offline_access. The sandbox shows a drop-down of simulated users (G6, G7, D1 and G7 15-day) and asks for no password.
- Swap the code for tokens within one minute. POST the code to /v3/oauth2/token from your server with grant_type=authorization_code. Store the refresh token at once.
- Pull glucose. Call dataRange to see which dates the user has, then pull egvs in windows of 30 days or less.
curl -X GET \ 'https://sandbox-api.dexcom.com/v3/users/self/egvs?startDate=2025-02-06T09:12:35&endDate=2025-02-07T09:12:35' \ -H 'Authorization: Bearer <token>'
Dexcom says sandbox data is simulated and may change or be removed, so do not use it for formal testing, validation or training algorithms.
Terms you must know
The Data Licensing Agreement is not public, so section numbers cannot be cited here. What Dexcom does publish:
- Non-negotiable agreement. You accept the agreement as written before Limited Access. For a healthcare product, have your counsel read it before you plan clinical workflows. For a wellness product, check it before you promise features to customers.
- HIPAA authorization. Each user completes a HIPAA authorization during sign-in. For a healthcare product, treat the data as PHI on your side. Whether Dexcom signs a BAA is not published, so ask. For a wellness product, you still hold sensitive health data and need consent and security to match.
- Medical use. Not published. A healthcare product that drives treatment decisions needs this answered first. A wellness app needs to know which claims it may make on screen.
- Storage, retention and AI training. Not published. A clinical program must keep records for its own rules. A wellness app that trains models on glucose data needs written permission.
- Branding, data selling, termination and competing products. Not published. Ask for each in writing. Termination terms decide what happens to stored data and connected patients if access ends.
- Partner upkeep. You must publish an app and keep at least one active user connected. A pilot that stalls after launch can lose partner status.
Cost and payment terms
- Developer registration: free.
- Limited and Full Access fees, revenue share or per-user charges: not published.
- End users need their own Dexcom CGM and account. Device cost is outside the API.
- Aggregator pricing, for example Junction: not part of this research. Ask the vendor.
Use cases
Diabetes remote patient monitoring
The patient signs in to Dexcom from your enrollment page and completes the HIPAA authorization. Your server stores the refresh token and polls egvs every hour or so. You compute time in range and flag patterns, then post a summary to the care team screen or to the EHR as FHIR Observations. Data used: glucose readings and trend, devices.
- Staff expect live alerts. The data is 1 hour late in the US. Set expectations in the program design and never sell it as urgent alerting.
- Refresh fails with HTTP 400. The user must sign in again. Show a reconnect task to staff and message the patient.
- No readings for days. Check devices and dataRange to tell a sensor gap from a broken connection.
Diabetes or metabolic digital therapeutic
The user links Dexcom inside your app. A background job pulls new glucose readings and events and feeds your coaching logic, which shows trends and lessons in the app. Data used: glucose readings, events.
- Coaching reacts to stale data. Show the time of the last reading next to every insight.
- You launch past 5 users without Full Access. Plan the Full Access review into the launch date.
Clinical trial glucose outcomes
Participants connect at the site visit. A nightly job pulls glucose in 30-day windows and writes to the study database. Data used: glucose readings, calibrations, devices.
- Backfill requests over 30 days fail with HTTP 400. Split by dataRange into 30-day windows.
- Gaps from sensor changes. Keep the devices record to explain gaps.
- Access path. Researchers apply through the Dexcom research portal. Start this early.
Payer or employer diabetes program
Members connect from the program portal. Weekly jobs compute engagement and time in range and send reports to coaches. Data used: glucose readings, data range.
- Members drop off silently. Track last reading date and prompt them.
- Partner status at risk if usage stops. Watch the active-user count.
Wellness and nutrition coaching app
A user with a Dexcom CGM links it to see glucose next to meals. Your app pulls glucose and events and plots them against logged meals. Data used: glucose readings, events.
- Users outside the US see 3-hour delays. Say so on the screen.
- Users want to share only glucose. Scopes are all or nothing. Explain this on the consent screen.
Dexcom data in an EHR or remote monitoring program
Most care teams want glucose next to the rest of the chart, 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.
| Dexcom value | FHIR Observation | Code |
|---|---|---|
| Estimated glucose value (egvs value) | Glucose in interstitial fluid, mg/dL | LOINC 99504-3 |
| Fingerstick calibration, or a bloodGlucose event | Glucose in capillary blood by glucometer, mg/dL | LOINC 41653-7 |
| Time in range you compute from egvs | Glucose readings in range out of all readings in the period | LOINC 97510-2 |
| Trend arrow and trendRate | Component or device-specific Observation | Your own code system. We found no LOINC code for the Dexcom trend arrow. |
Keep the Dexcom recordId on each Observation so a re-pull does not create a duplicate. Map 39 and 401 with care: they mean below 40 and above 400, not exact values. If a user revokes access at Dexcom.com, Dexcom stops sending new data but says data already shared is not affected, so your own retention rules decide what happens to it.
Known blockers and gotchas
- 5-user cap. Limited Access stops at 5 users. Book the Full Access review before you promise a launch date.
- No push. Poll on a schedule and keep under 60,000 calls per app per hour. Back off on HTTP 429.
- One-minute codes. The authorization code expires after one minute. Exchange it right away on your server.
- Single-use refresh tokens. Each refresh returns a new token. Save it before you use the access token, or a crash leaves the user disconnected.
- Tokens expire within a year. Plan a reconnect prompt.
- 30-day window. Longer queries return HTTP 400.
- TLS 1.3 required. Check older servers and proxies.
- Agreement before data. The Data Licensing Agreement is non-negotiable and not public. Get it in front of counsel as soon as Dexcom shares it, before you design clinical features around the data.
- Partner status can lapse. You must publish a Full Access app and keep at least one active user connected within 60 days of launch and at all times after. A paused pilot can put this at risk.
- Dexcom can ask for changes. The Full Access review can require implementation or screen fixes. Leave time in the plan for one round of changes.
- Redirect URI must match exactly. A mismatch fails the sign-in. Register every environment's URI.
- Region base URLs. US, EU and Japan users use different hosts. Store the region per user.
Delivery timeline
Our estimate. Vendor steps have no published wait time.
| Week | Work | Depends on Dexcom? |
|---|---|---|
| 1 | Register, sandbox OAuth, pull egvs and devices, token store with refresh | No |
| 2 to 3 | Sync job with 30-day windows, dataRange backfill, 429 handling, FHIR mapping, consent screens | No |
| Parallel from week 1 | Limited Access application and Data Licensing Agreement | Yes |
| After Limited Access | Test with up to 5 real users | Yes |
| Before launch | Full Access questionnaire, technical and commercial review, fixes Dexcom asks for | Yes. This is the critical path. |
Questions to ask Dexcom before you sign
- What does Limited and Full Access cost, and is there a per-user fee or revenue share?
- How long do the Limited Access and Full Access reviews usually take?
- Will you sign a BAA with us?
- What does the Data Licensing Agreement say about medical use, AI training, data retention and data selling?
- Is there a real-time, partner or push option for our use case?
- How far back can we read a new user's history?
- If we use an aggregator, does its Dexcom approval cover us?
- What branding and screen rules apply to the Full Access review?
Other device integration guides
Dexcom 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
- Fitbit and Google Health API integration guide
- Apple Health API integration guide
- Health Connect API integration guide
- Samsung Health API integration guide
- Withings 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
Plan your Dexcom integration with us
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
- Base URLs: sandbox https://sandbox-api.dexcom.com, US https://api.dexcom.com, EU and rest of world https://api.dexcom.eu, Japan https://api.dexcom.jp.
- Auth: OAuth 2.0 authorization code. Login GET /v3/oauth2/login (a browser redirect), token POST /v3/oauth2/token with Content-Type application/x-www-form-urlencoded. scope=offline_access, response_type=code. redirect_uri must match the registered value.
- Token rules: code single-use, 1-minute life. Access token expires_in 7200 s. Refresh token single-use, max 1 year, rotated on each refresh. HTTP 400 on refresh means re-authorize.
- Endpoints (all GET): /v3/users/self/egvs, /events, /calibrations, /alerts, /devices, /dataRange. Query parameters startDate and endDate (ISO 8601, start inclusive, end exclusive, matched on systemTime). Each window spans at most 30 days, except dataRange. /devices takes no parameters. /dataRange takes an optional lastSyncTime.
- Scopes shown to users: Estimated Blood Glucose Levels, Calibration Data, Events Entry Data, Device Details. All or nothing.
- Rate limit: 60,000 calls per app per hour, HTTP 429 above. TLS 1.3 required.
- Webhook signing: not applicable, no webhooks published.
- FHIR: map each egv to an Observation with valueQuantity in mg/dL. Use LOINC 99504-3 (Glucose [Mass/volume] in Interstitial fluid) for each egv. Do not reuse capillary codes. Calibrations and bloodGlucose events: LOINC 41653-7 (Glucose [Mass/volume] in Capillary blood by Glucometer). Both checked on the NLM LOINC search, 11 Nov 2026.
- Version: v3. Sunset dates for earlier versions are not published.
Sources
- Dexcom G7 and Apple Health, https://www.dexcom.com/en-us/faqs/how-do-i-share-my-glucose-data-with-the-apple-health-app, read 10 November 2026.
- Stelo and health apps, https://www.stelo.com/en-us/faqs/using-stelo/how-do-i-share-my-glucose-data-with-health-apps, read 10 November 2026.
- Terra supported integrations, https://docs.tryterra.co/reference/health-and-fitness-api/supported-integrations, 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.
- Dexcom API v3 endpoint overview, https://developer.dexcom.com/docs/dexcomv3/endpoint-overview/, read 10 Nov 2026.
- Dexcom scopes and access levels, https://developer.dexcom.com/docs/dexcom/scopes-access, read 10 Nov 2026.
- Dexcom authentication, https://developer.dexcom.com/docs/dexcom/authentication, read 10 Nov 2026.
- Junction Dexcom v3 guide, https://docs.junction.com/wearables/guides/dexcom_v3.md, search listing only, read 10 Nov 2026.
Ready to scale?
Talk to our healthcare engineering team about building, integrating, and shipping faster.
Frequently Asked Questions
Does Dexcom have a public API?
Is the Dexcom API real time?
How much does the Dexcom API cost?
How many users can I connect before approval?
Does Dexcom offer webhooks?
Which Dexcom devices does the API support?
Will Dexcom sign a BAA?
How much history can I pull?
Can users share only their glucose data?
How long do Dexcom tokens last?
Which OAuth scope do I request for the Dexcom API?
How do I pull only new Dexcom data?
Are Dexcom glucose values in mg/dL or mmol/L?
What do the values 39 and 401 mean?
Which time field should I use, systemTime or displayTime?
Can I test without a Dexcom sensor?


