Hoppa till huvudinnehallet

Dexcom CGM Integration

Partnership required

Dexcom API access is granted via developer application. You need a Dexcom developer account and an approved redirect URI before going live. vitalera handles the sandbox → production promotion for partner organisations.

Dexcom is the global leader in continuous glucose monitoring (CGM). The vitalera Dexcom integration uses Dexcom API v3 and is FDA-cleared for third-party platforms receiving CGM data for clinical use.

Data types​

EndpointSignalLOINC
/egvsEstimated glucose values (5-minute cadence)2339-0
/events (insulin)Insulin doses (units, fast/long-acting)—
/events (carbs)Carb entries (grams)9059-7
/events (exercise)Exercise events (duration, intensity)—

All glucose values are normalised to mg/dL (Dexcom API already returns mg/dL).

Connection​

curl -X POST https://api.vitalera.io/api/connected-accounts/dexcom/oauth/initiate/ \
  -H "Authorization: Bearer <user_token>"

Sandbox vs production​

Set the environment flag DEXCOM_USE_SANDBOX=true on the vitalera side to route through Dexcom's sandbox endpoint (https://sandbox-api.dexcom.com). Sandbox returns pre-canned users with synthetic but clinically realistic glucose traces.

Polling cadence​

Dexcom does not push. vitalera polls /egvs per connection every 5–15 minutes depending on the tenant's entitlement tier. Historical backfill supports up to 90 days.

Clinical notes​

  • 3-hour minimum latency applies to real-time glucose values when used for clinical decisions, per Dexcom's developer agreement. vitalera enforces this on any patient-facing alarm.
  • Dexcom G7 users on firmware 2.x expose HR and SpO2 via linked smartwatch pairing; those signals are surfaced via the apple_health / health_connect SDK route, not the Dexcom API.

Next steps​