Care teams want glucose data in the same place as every other reading. The Dexcom API makes that possible for patients who already wear a Dexcom continuous glucose monitor (CGM). Tenovi connects to the Dexcom API to bring patient-authorized CGM data into its remote patient monitoring (RPM) dashboard. Clinicians see it next to blood pressure, weight, and other vitals.
This guide starts with a short background on remote glucose monitoring. Next, it explains what the Dexcom API does and how the Tenovi connection works. The final sections cover benefits, clinical workflow, and common questions.
A Short Background on Remote Glucose Monitoring
For decades, home glucose tracking meant a fingerstick and a paper logbook. Patients pricked a finger, read the meter, and carried the numbers to their next visit. Connected glucometers changed that by sending each reading to the care team automatically. Tenovi’s cellular and Gateway-connected glucometers work this way.
Continuous glucose monitoring went further. A small sensor reads glucose in the fluid just under the skin every few minutes, day and night. Clinicians see the full daily curve instead of a few snapshots, including overnight patterns and after-meal rises. Our guide to CGM covers the technology in more detail.
National guidance now supports wider CGM use. The American Diabetes Association’s 2026 Standards of Care recommend CGM at diabetes onset and anytime after for people using insulin. The recommendation also covers people on other therapies that can cause hypoglycemia. It extends to any diabetes treatment where CGM helps with management.
A 2026 study in Endocrine Practice looked at RPM paired with CGM at a Bronx safety-net hospital. Adults with poorly controlled type 2 diabetes in the RPM program had monthly telemedicine visits with an endocrine specialist. In that group, 58.5% reached the study’s HbA1c target, compared with 36.2% of patients receiving standard care.
Remote glucose monitoring sends readings to the care team between office visits. Tenovi’s overview of remote glucose monitoring explains how connected meters fit into diabetes care.
What is the Dexcom API?
The Dexcom API is Dexcom’s official channel for sharing CGM data with outside software. It is a REST API that uses the OAuth 2.0 standard for authorization. Software companies apply to Dexcom’s developer program, and Dexcom reviews each request for production access. Approved apps can retrieve estimated glucose values, device details, and events a patient logs, such as carbohydrates or exercise.
Patient consent sits at the center of the design. Dexcom’s developer FAQ explains that apps get no automatic access to user data. The patient signs in with Dexcom and grants a HIPAA authorization before any data is shared. Patients can revoke that authorization at any time from their Dexcom account.
Timing is the other key detail. Dexcom’s API documentation describes a one-hour delay for US data from its G6 and G7 apps. Dexcom positions the API for reviewing past CGM data and metrics. It also states that real-time treatment decisions should not rely on data delivered this way.
Understanding How Tenovi Connects to the Dexcom API
Tenovi announced its Dexcom integration in July 2025. Through the Dexcom API, Tenovi pulls each enrolled patient’s authorized CGM data into the Tenovi dashboard. Patients keep wearing their own Dexcom sensor and using the Dexcom app.
In the Tenovi Web App, Dexcom CGM is a virtual device. Tenovi ships no hardware for it, and no Tenovi Gateway is needed. Tenovi manages the Dexcom connection, so client teams handle setup and data review inside Tenovi. Dexcom data is viewable in the Tenovi dashboard only. It isn’t sent through Tenovi’s API or webhooks.
Step-by-Step Patient Setup
Staff complete a few steps in Tenovi, and the patient signs in once. Tenovi’s Dexcom client guide lays out the process.
- Create the patient in the Tenovi web app with an email address. For an existing patient, confirm one is on file.
- From the patient’s RPM profile, click the button to add a device. If the patient already has a device, add one from the RPM Devices tab in Edit Patient.
- Select Dexcom CGM from the device list and click Add Device. The option stays grayed out if the patient has no email address.
- Tenovi emails the patient a request to connect their Dexcom account, with a Link Account button.
- The patient signs in on Dexcom’s website with their Dexcom login. A Tenovi page then confirms “Account Connected,” or shows an error page if something went wrong.
- The device receives a unique ID and moves from Pending to Delivered on the device dashboard.
- From then on, Tenovi pulls the patient’s glucose data from Dexcom every hour.
Because sign-in happens on Dexcom’s site, the patient’s Dexcom password never passes through Tenovi or the care team.
What Care Teams Can See
Tenovi displays hourly average glucose data in each patient’s RPM profile. A Dexcom CGM card shows the average estimated glucose value for the last 7 and 30 days. An Estimated Glucose Value chart plots the data over a selectable time span, and a table view shows the numbers. Dexcom sensors report values from 40 to 400 mg/dL.
Clinicians can review this data alongside readings from Tenovi blood pressure monitors, scales, pulse oximeters, and other devices. A care manager preparing for a call can find glucose and other vitals in one place.
Benefits of Dexcom Remote Patient Monitoring Through Tenovi
Dexcom remote patient monitoring through Tenovi adds CGM data to a program without adding CGM logistics. Here is what that looks like day to day.
No CGM Inventory to Manage
Patients get Dexcom sensors through their prescriber and pharmacy. Your team has no CGM stock to buy, store, ship, or replace. Enrolling a Dexcom user takes one device entry in Tenovi and one patient sign-in.
Glucose Trends Beside Every Other Vital
Many patients in cardiometabolic programs manage diabetes alongside high blood pressure or heart failure. Their care team needs to see how those conditions move together. With Dexcom data in Tenovi, glucose averages sit beside blood pressure and weight trends. Nobody has to switch between portals to prepare for a check-in.
One Simple Step for Patients
The patient approves the connection once, with their existing Dexcom login. They keep their sensor routine, their Dexcom app, and their alerts. There is no new device to charge, pair, or learn.
Fingerstick and CGM Patients in One Program
Glucose programs usually include a mix of patients. Some wear a CGM. Others check with a meter, by preference or because of coverage. Tenovi supports both. A patient on the Tenovi Cellular Glucometer and a patient on Dexcom can share one program and one dashboard.
Consent and Security You Can Explain
Data access rests on the patient’s own authorization through Dexcom. Tenovi is HIPAA compliant and SOC 2 Type 2 compliant. Care teams can explain the process simply. The patient approves the connection and can turn it off whenever they choose.
Who Can Use Dexcom Data Through Tenovi
Dexcom data in Tenovi serves care teams that work in the Tenovi dashboard.
- Health systems and practices can support patients who already wear a Dexcom. No extra glucose hardware has to go out the door.
- Health plans and employer-sponsored programs focused on cardiometabolic care can include CGM users in the same monitoring model.
- Care management teams can review CGM trends next to blood pressure and weight before each patient call.
Software platforms that connect through Tenovi’s API can use Tenovi glucometers for glucose data. The FAQ on API access covers how that works.
How Hourly Data Fits Clinical Workflow
Hourly averages are built for trend review. A care manager can scan a week of data before a scheduled call. They can look for recurring overnight patterns or check how glucose changed after a medication adjustment. In the Bronx study, the most frequent medication changes involved insulin and GLP-1 therapies.
Real-time readings and alerts stay with the patient’s Dexcom app. Dexcom data reaches its API about an hour after upload, and Tenovi pulls new data hourly. Programs should explain this to patients at enrollment. The care team reviews glucose trends on a schedule and does not watch readings minute by minute. Patients should keep following their clinician’s instructions for high and low glucose.
Frequently Asked Questions About the Dexcom API
1) What is the Dexcom API used for?
The Dexcom API lets approved software access CGM data that a patient chooses to share. Health apps, research tools, and remote monitoring platforms use it to show glucose trends and CGM metrics. Tenovi uses it to bring Dexcom data into its RPM dashboard alongside other vitals.
2) Is Dexcom data in Tenovi available in real time?
Dexcom data in Tenovi runs on a delay. Dexcom makes app-uploaded data available through its API one hour later in the United States. Tenovi then pulls new data every hour. The integration supports trend review, while the patient’s Dexcom app handles real-time readings and alerts.
3) Does Tenovi supply Dexcom CGM sensors?
Patients get their Dexcom systems through their prescriber and pharmacy. In Tenovi, Dexcom CGM is a virtual device, so nothing ships from Tenovi for it. For its own connected devices, including blood pressure monitors, scales, and glucometers, Tenovi handles fulfillment, provisioning and support.
4) How does a patient connect their Dexcom account to Tenovi?
The care team adds Dexcom CGM to the patient’s profile in Tenovi. The patient then receives an email with a Link Account button. They sign in on Dexcom’s website and land on a Tenovi page confirming the connection. An email address on file is required for this step.
5) Can a patient stop sharing Dexcom data?
Patients can stop sharing whenever they choose. Dexcom lets users revoke third-party access from the permissions area of their Dexcom account. Once access is revoked, new data no longer reaches Tenovi.
6) Which Dexcom systems work with the Dexcom API?
Dexcom’s API documentation lists G6, G7, and G7 15-day systems among the devices it supports in the United States. Ask your Tenovi team which systems your program can enroll before you begin.
7) Can Dexcom data flow into our own platform through Tenovi’s API?
Dexcom data is viewable in the Tenovi dashboard only. Dexcom glucose readings and device management aren’t available through Tenovi’s API. Platforms that need glucose data in their own software can use Tenovi glucometers instead. Each reading arrives at your webhook in mg/dL as it’s taken. You can also pull readings for any patient from the measurements API. The API returns individual readings, so your platform calculates averages and other metrics.
Understanding the Dexcom API
The Dexcom API gives patients a secure, consent-based way to share CGM data with the programs that support their care. Remote glucose monitoring has grown from paper logbooks to connected meters to continuous sensors. Current ADA guidance supports broader CGM use. Tenovi connects to the Dexcom API so care teams can review hourly glucose averages in the Tenovi dashboard. Patients keep their own sensors and Dexcom app, and programs carry no CGM inventory. Because the data arrives hourly, it suits trend review and care planning. Real-time alerts stay on the patient’s device.
Tenovi is remote monitoring infrastructure for RPM software companies, chronic care management companies, telehealth platforms, health systems, payers, and pharmacies. One partner and one API give you more than 60 cellular-connected devices. Dexcom CGM data appears beside them in the Tenovi dashboard. We handle fulfillment, provisioning and support. Contact us for a free demo and consultation.
