Device IntegrationHealthcare Interoperability

Dexcom API Integration Guide 2026: CGM Data Access

July 8, 202615 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.

Dexcom API Integration Guide 2026: CGM Data Access

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

QuestionShort 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 buildAbout 3 weeks of engineering. Vendor approval time comes on top. Our estimate.

Integration strategies

RouteOwn mobile app?Own server?Vendor approval or contract?SDK?LatencySupported dataNot supportedBest for
Dexcom API v3 (cloud REST)No. A web sign-in page works.YesYes. Free sandbox, then Limited Access (5 users) and Full Access review, plus a Data Licensing Agreement.No1 hour US, 3 hours outside USGlucose readings, events, calibrations, alerts, devices, data rangeReal-time glucose, partial scopes, pushMost clinical and wellness products
Webhooks or pushNot published. All v3 endpoints are GET, so you poll.
Phone SDKNot published on the developer site.
Partner or real-time APINot published on the developer site. Ask Dexcom directly.
Apple Health or Health ConnectG7 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)NoYes, to receive data from the aggregatorContract with the aggregator. Dexcom approval terms through an aggregator are not published.Aggregator SDK or APIAt best the Dexcom delayJunction documents a Dexcom v3 providerAnything Dexcom v3 lacksTeams already using Junction for other devices
Aggregators, checked 10 November 2026Terra 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 exportNot 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

QuestionBuild in-houseWearable aggregatorBuild with a partner (Nirmitee)
Whose Dexcom app and approval?YoursDepends 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 AgreementYou accept it and your counsel reads itNot published whether the aggregator's agreement covers youYou accept it. We design storage and screens around it.
Polling and token rotationYou build and run themThe aggregator runs themWe build them, then hand them to you or run them
Data modelDexcom's own fieldsThe aggregator's schemaFHIR Observations for your EHR or remote monitoring stack
Other devices laterOne new build per deviceMany devices through one APISame pattern reused across devices
Time to first real userDepends on your teamDepends on the aggregator's onboardingAbout 3 weeks of build in our estimate, plus Dexcom approval time
Cost shapeEngineering timeAggregator fee. Pricing for Dexcom on these platforms is not published.Project fee, scoped after a call
Every way to get Dexcom data, and what each one needs.

What data you can get

Data typeGranularityHistoryPush or pull
Estimated glucose values (egvs)Each reading, in mg/dL, with trend rate in mg/dL/minNot published. Use dataRange per user. Max 30 days per request.Pull
EventsEach user-entered eventSamePull
CalibrationsEach fingerstick calibrationSamePull
AlertsEach alert recordSamePull
DevicesDevice recordsSamePull
Data rangeThe span of data held for the userNot limited to 30 daysPull

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.

FieldWhat it holds
recordIdA unique id for the reading. Use it to avoid duplicates when windows overlap.
systemTime and displayTimesystemTime is UTC by the device clock. displayTime is the time shown to the user. Phone records carry a UTC offset, receiver records do not.
valueGlucose 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 trendRateThe arrow, such as flat, singleUp or doubleDown, and the rate in mg/dL/min behind it
transmitterGeneration, displayDevice, displayAppThe sensor generation (for example g6 or g7), the display (receiver, iOS or android) and the app
transmitterId, transmitterTicksA 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

ItemWhat Dexcom publishesWhat it means for you
G6, G7, G7 15-daySupported by API v3These are the sensors your US users will have.
Dexcom ONE, ONE+Supported by API v3, not sold in the USOnly relevant if you also serve users outside the US.
US hosthttps://api.dexcom.com, 1-hour delayDefault for US programs.
EU and rest of world hosthttps://api.dexcom.eu, 3-hour delayStore each user's region and call the matching host.
Japan hosthttps://api.dexcom.jpSeparate host. Plan for it only if you serve Japan.
Receiver uploadsDexcom Uploader over USB, available immediatelyOnly 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

  1. Register for free on developer.dexcom.com. You get apps, credentials, sandbox data and support requests. You can start the same day.
  2. Build against the sandbox at https://sandbox-api.dexcom.com.
  3. 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.
  4. 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.
  5. 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.
  6. 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

  1. 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.
  2. 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.
  3. 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.
  4. 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

Glucose from Dexcom to the care team, step by step.

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 valueFHIR ObservationCode
Estimated glucose value (egvs value)Glucose in interstitial fluid, mg/dLLOINC 99504-3
Fingerstick calibration, or a bloodGlucose eventGlucose in capillary blood by glucometer, mg/dLLOINC 41653-7
Time in range you compute from egvsGlucose readings in range out of all readings in the periodLOINC 97510-2
Trend arrow and trendRateComponent or device-specific ObservationYour 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.

WeekWorkDepends on Dexcom?
1Register, sandbox OAuth, pull egvs and devices, token store with refreshNo
2 to 3Sync job with 30-day windows, dataRange backfill, 429 handling, FHIR mapping, consent screensNo
Parallel from week 1Limited Access application and Data Licensing AgreementYes
After Limited AccessTest with up to 5 real usersYes
Before launchFull Access questionnaire, technical and commercial review, fixes Dexcom asks forYes. This is the critical path.

Questions to ask Dexcom before you sign

  1. What does Limited and Full Access cost, and is there a per-user fee or revenue share?
  2. How long do the Limited Access and Full Access reviews usually take?
  3. Will you sign a BAA with us?
  4. What does the Data Licensing Agreement say about medical use, AI training, data retention and data selling?
  5. Is there a real-time, partner or push option for our use case?
  6. How far back can we read a new user's history?
  7. If we use an aggregator, does its Dexcom approval cover us?
  8. 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.

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?

Yes. Dexcom API v3 is a REST API with OAuth 2.0. Registration on developer.dexcom.com is free and gives you sandbox data the same day.

Is the Dexcom API real time?

No. US data is delayed about 1 hour and data outside the US about 3 hours. Receiver uploads through Dexcom Uploader over USB are available right away.

How much does the Dexcom API cost?

Registration is free. Dexcom does not publish fees, revenue share or per-user charges for Limited or Full Access, so ask during the partnership request.

How many users can I connect before approval?

Limited Access allows up to 5 authorized users for testing with real data. Serving more needs Full Access, which follows a technical and commercial review by Dexcom.

Does Dexcom offer webhooks?

None are published. All v3 endpoints are GET requests, so you poll on a schedule within the limit of 60,000 calls per app per hour.

Which Dexcom devices does the API support?

The v3 API supports G6, G7, G7 15-day, Dexcom ONE and Dexcom ONE+. Dexcom says ONE and ONE+ are not sold in the US.

Will Dexcom sign a BAA?

Dexcom does not publish its BAA stance. Users do complete a HIPAA authorization during sign-in. Ask Dexcom directly before you sign the Data Licensing Agreement.

How much history can I pull?

Each request covers at most 30 days, and longer windows return HTTP 400. Dexcom does not publish a total history limit, so call the dataRange endpoint for each user.

Can users share only their glucose data?

No. Scopes are all or nothing. Users approve glucose, calibrations, events and device details together.

How long do Dexcom tokens last?

Access tokens last 2 hours. Refresh tokens are single-use, rotate on each refresh and last at most one year. An HTTP 400 on refresh means the user must sign in again.

Which OAuth scope do I request for the Dexcom API?

Only offline_access, with response_type=code. The user then sees four data scopes on the Dexcom page: Estimated Blood Glucose Levels, Calibration Data, Events Entry Data and Device Details. You cannot ask for fewer.

How do I pull only new Dexcom data?

Call dataRange with the lastSyncTime parameter set to your last sync. Dexcom then returns date ranges only for data that arrived after that time. Pull egvs and events for those ranges, in windows of 30 days or less.

Are Dexcom glucose values in mg/dL or mmol/L?

Dexcom says all glucose values come in mg/dL and trend rates in mg/dL/min. Converting to mmol/L is up to your app. Read the unit field on each record anyway, since the field allows both.

What do the values 39 and 401 mean?

They are out-of-range markers. 39 means the reading was below 40 mg/dL and 401 means it was above 400 mg/dL. The status field says low or high. Do not chart them as exact readings.

Which time field should I use, systemTime or displayTime?

Queries run on systemTime, which is UTC by the device clock. displayTime is what the user saw on the device and can be changed by the user. Dexcom notes systemTime is not true UTC because of clock drift. Phone records include a UTC offset, receiver records do not, and dataRange never does.

Can I test without a Dexcom sensor?

Yes. The sandbox has simulated G6, G7, D1 and G7 15-day users with no password. Each user has a different date range, so call dataRange first. Dexcom says the sandbox is not for formal testing or algorithm training.
Share