Skip to content
Wearable Integrations

Platform integration

Continuous Glucose Monitor Integration

Continuous glucose monitors (CGMs) measure interstitial glucose every few minutes and are central to modern diabetes care. Access to that data varies widely by manufacturer: some offer a developer API with an approval process, others make data available only through partnership or commercial agreements.

We help diabetes, care management and research teams choose a realistic access route for each CGM brand, design a glucose data model that handles units and timing correctly, and present derived metrics in a way that is clearly labeled and validated.

Dexcom, FreeStyle Libre, LibreView and Medtronic are trademarks of their respective owners. We do not claim partnerships with any CGM manufacturer, and we verify current access programs, data delays and terms with vendor documentation at project start.

Key points

  • Access routes differ by CGM manufacturer
  • Production access usually needs vendor approval
  • API data may be delayed relative to real time
  • Regulatory review needed for alarms or dosing support

CGM Integration: at a glance

Summary based on publicly available vendor documentation. Vendor terms, endpoints and limits change; we verify them against current documentation at the start of every project.

Integration methods
  • Dexcom developer API (OAuth 2.0, sandbox with simulated data)
  • LibreView data access through partnership or commercial agreement
  • Apple HealthKit and Health Connect where vendor apps write glucose
  • Partnership-only arrangements for other manufacturers such as Medtronic
Data types
  • Estimated glucose values (EGVs)
  • Calibrations and user-logged events
  • Alerts and alert settings, where exposed
  • Device and sensor session information
  • Derived metrics such as time in range and GMI (calculated, labeled)
Authorization requirements
  • User authorizes data sharing via the vendor's OAuth flow
  • Users enable writing to Apple Health or Health Connect in vendor apps
  • Partner programs may require contracts and security review
  • Consent must cover each downstream use of glucose data
Developer approval & agreements
  • Dexcom: production access requires application and approval
  • Abbott FreeStyle Libre: no general public API; LibreView access typically by agreement
  • Medtronic: partnership-only
  • Terms and programs verified against vendor documentation at project start
API limitations
  • Public API data may be delayed relative to real time; check current terms
  • Real-time access is typically arranged through partner agreements
  • Health platform syncs may be delayed or incomplete
  • Sampling intervals differ by device and model
  • Units vary between mg/dL and mmol/L
Healthcare use cases
  • Diabetes care management and coaching
  • Remote monitoring for type 1 and type 2 diabetes
  • Clinical research and trials
  • Gestational diabetes and perioperative programs
  • Population health reporting on glycemic metrics

Supported integration methods

The access route depends on the manufacturer, the market and the type of product you are building. Many diabetes platforms combine a direct vendor API for one brand with health platform data for others.

Before development starts, we list the CGM models your users actually wear, the countries you operate in and how quickly the data needs to arrive. That inventory usually determines which vendor conversations are needed and whether a health platform route is sufficient for a first release.

Dexcom developer API

A REST API with OAuth 2.0 and a sandbox that provides simulated data. Production access requires an application and approval. Data through the public API has historically been delayed relative to real time in some regions and products; real-time access is arranged through partner agreements. We check current terms before design.

Abbott FreeStyle Libre

There is no general public API. Access to LibreView data typically requires a partnership or commercial agreement with Abbott.

Health data platforms

Some Libre and Dexcom apps can write glucose to Apple HealthKit or Health Connect when the user enables it, sometimes with a delay. This can be a practical route for wellness or coaching products.

Other manufacturers

Medtronic and several other CGM makers provide data access only through partnerships. We help you prepare for those conversations with a clear technical scope.

Glucose data types and derived metrics

The core record is the estimated glucose value (EGV). Dexcom G6 and G7 typically produce a value every five minutes; FreeStyle Libre sensors may provide per-minute current readings and 15-minute history depending on model. Calibrations, events, alerts and device information add context where the source exposes them.

Derived metrics such as time in range (70 to 180 mg/dL per international consensus), glucose management indicator (GMI) and glycemic variability are useful, but they are calculations, not device outputs. We label them clearly, document the method and data sufficiency rules, and validate them against reference calculations.

  • Store the original unit and convert between mg/dL and mmol/L explicitly
  • Keep device timestamps and handle sensor warm-up and gaps
  • Deduplicate values that arrive from more than one source

Authorization and access requirements

Patients authorize sharing through the vendor's OAuth flow or by enabling health platform sync in the vendor app. Your consent model should explain who sees the data, how often it updates and whether it is monitored in real time.

On the business side, production API access, partner programs and commercial agreements are the norm rather than the exception for CGM data. We build these steps into the project timeline and confirm requirements with each vendor's current documentation. Security and privacy controls follow your HIPAA-aligned integration approach.

Limitations and regulatory considerations

Data delays matter. If glucose data through an API or health platform is delayed, it should not be presented as live, and it should not drive urgent alerts. Interfaces must show the reading time clearly.

Software that displays CGM data alongside alarms, or that informs or drives dosing decisions, may be regulated as a medical device. iCGM designations, alternate controller enabled (ACE) pumps and automated insulin delivery systems are outside the scope of a simple data integration. We recommend obtaining regulatory advice early when your product approaches these areas.

Healthcare use cases

CGM data supports diabetes care management, coaching programs, remote patient monitoring for people with type 1 or type 2 diabetes, gestational diabetes programs and clinical research. Retrospective review of glucose patterns is often the safest starting point.

Glucose data can be shared with clinical systems through EHR integration or FHIR Observations, with derived metrics clearly identified as calculated values.

Frequently asked questions

Does every CGM brand have a public API?

No. Dexcom offers a developer API with an approval process. Abbott FreeStyle Libre has no general public API, and LibreView access typically requires an agreement. Medtronic access is partnership-only.

Is CGM data from APIs real time?

Not always. Data through Dexcom's public API has historically been delayed in some regions and products, and health platform syncs can lag. Check current vendor terms before designing any time-sensitive feature.

Can we read glucose from Apple Health or Health Connect instead?

Some Dexcom and Libre apps write glucose to these platforms when the user enables it, sometimes with a delay. This can work for coaching or wellness products but is not suited to urgent alerts.

How should time in range be calculated?

Time in range is commonly defined as 70 to 180 mg/dL per international consensus. We document the method, data sufficiency rules and unit handling, and label it as a derived value.

Will our CGM software be regulated?

It can be. Software that shows CGM data with alarms or supports dosing decisions may be regulated as a medical device. We recommend specialist regulatory advice for those features.

Plan your CGM data integration

Tell us which CGM brands your users have and how you plan to use the data. We will map realistic access routes, approval steps and data handling requirements.