Dexcom
Dexcom is a leading medical device company that develops, manufactures, and distributes continuous glucose monitoring (CGM) systems for people with diabetes. The company's wearable sensors stream real-time glucose data to mobile apps, dedicated receivers, and connected health platforms. Dexcom exposes a public developer program that lets approved third parties retrieve CGM data (estimated glucose values, events, calibrations, alerts, devices, and data range) through an OAuth 2.0 secured REST API, with a sandbox for development and a production environment for live patient data.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Dexcom the way a machine reads it — 109 machine-readable artifacts across 7 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Dexcom scores 64.3/100 (strong), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Dexcom
Each block below is one kind of artifact we hold for Dexcom. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 7
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Dexcom Alerts API
Alert events generated by the user's CGM display device.
Dexcom Authentication API
OAuth 2.0 authorization and token operations.
Dexcom Calibrations API
User calibration entries from fingerstick blood glucose meter readings.
Dexcom Data Range API
Earliest and latest record times available for the authorized user.
Dexcom Devices API
Information about the user's CGM transmitters and display devices.
Dexcom Estimated Glucose Values API
Time-series CGM glucose readings for the authorized user.
Dexcom Events API
User-entered events such as carbohydrate intake, insulin doses, exercise, and health events.
Scroll within the panel for all 7 ·
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Dexcom Developer API
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Dexcom Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Dexcom Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Dexcom Finops
FINOPSFeatures 9
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Continuous Glucose Monitoring Data
Retrieve estimated glucose values (EGVs) at 5-minute intervals across G6, G7, Dexcom ONE, and ONE+ systems.
User-Entered Events
Access user-logged carbs, insulin, exercise, and health events alongside CGM data.
Calibrations
Read fingerstick BG meter calibration entries for transmitters that require them.
Alerts
Read CGM display device alerts (high, low, urgent low, rise, fall, no readings, out-of-range).
Device Inventory
List the user's transmitters and display devices, including alert schedules and settings.
Data Range
Discover earliest and latest record times for efficient incremental sync.
Multi-Region Hosts
Production hosts in the US (api.dexcom.com), EU (api.dexcom.eu), and Japan (api.dexcom.jp).
Sandbox Environment
Test against simulated CGM data without real Dexcom credentials at sandbox-api.dexcom.com.
OAuth 2.0 Authorization Code
Standards-based user consent and token issuance with offline_access (refresh) support.
Scroll within the panel for all 9 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Dexcom Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Dexcom API Rules
SPECTRALDexcom API Rules
SPECTRALJSON Schema 27
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
AlertName
JSON SCHEMAAlertRecord
JSON SCHEMAAlertSchedule
JSON SCHEMAAlertSetting
JSON SCHEMAAlertState
JSON SCHEMAAlertsResponse
JSON SCHEMACalibrationRecord
JSON SCHEMACalibrationsResponse
JSON SCHEMADataRangeMoment
JSON SCHEMADataRangeResponse
JSON SCHEMADataRangeWindow
JSON SCHEMADateTime
JSON SCHEMADeviceRecord
JSON SCHEMADevicesResponse
JSON SCHEMAEGVRecord
JSON SCHEMAEgvStatus
JSON SCHEMAEgvsResponse
JSON SCHEMAEventRecord
JSON SCHEMAEventStatus
JSON SCHEMAEventType
JSON SCHEMAEventsResponse
JSON SCHEMAGlucoseUnit
JSON SCHEMARateUnit
JSON SCHEMATokenRequest
JSON SCHEMATokenResponse
JSON SCHEMATransmitterGeneration
JSON SCHEMATrendType
JSON SCHEMAScroll within the panel for all 27 ·
JSON Structure 27
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Dexcom Api Alert Name Structure
JSON STRUCTUREDexcom Api Alert Record Structure
JSON STRUCTUREDexcom Api Alert Schedule Structure
JSON STRUCTUREDexcom Api Alert Setting Structure
JSON STRUCTUREDexcom Api Alert State Structure
JSON STRUCTUREDexcom Api Alerts Response Structure
JSON STRUCTUREDexcom Api Calibration Record Structure
JSON STRUCTUREDexcom Api Calibrations Response Structure
JSON STRUCTUREDexcom Api Data Range Moment Structure
JSON STRUCTUREDexcom Api Data Range Response Structure
JSON STRUCTUREDexcom Api Data Range Window Structure
JSON STRUCTUREDexcom Api Date Time Structure
JSON STRUCTUREDexcom Api Device Record Structure
JSON STRUCTUREDexcom Api Devices Response Structure
JSON STRUCTUREDexcom Api Egv Record Structure
JSON STRUCTUREDexcom Api Egv Status Structure
JSON STRUCTUREDexcom Api Egvs Response Structure
JSON STRUCTUREDexcom Api Event Record Structure
JSON STRUCTUREDexcom Api Event Status Structure
JSON STRUCTUREDexcom Api Event Type Structure
JSON STRUCTUREDexcom Api Events Response Structure
JSON STRUCTUREDexcom Api Glucose Unit Structure
JSON STRUCTUREDexcom Api Rate Unit Structure
JSON STRUCTUREDexcom Api Token Request Structure
JSON STRUCTUREDexcom Api Token Response Structure
JSON STRUCTUREDexcom Api Transmitter Generation Structure
JSON STRUCTUREDexcom Api Trend Type Structure
JSON STRUCTUREScroll within the panel for all 27 ·
Examples 17
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Scroll within the panel for all 17 ·
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 6
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Diabetes Self-Management Apps
Consumer apps that visualize glucose trends alongside insulin, food, and activity logs.
Clinical Decision Support
Provider tools that aggregate CGM data into time-in-range and ambulatory glucose profile (AGP) views.
Clinical Research
Studies analyzing glycemic patterns, intervention response, or device performance across cohorts.
Coaching and Behavior Change
Health-coaching platforms correlating CGM signals with meals, workouts, and sleep.
AI-Assisted Glucose Management
LLM and agentic systems that reason over CGM history via MCP tools to recommend actions.
Connected Health Platforms
Aggregators (Apple Health, Validic, Tidepool, etc.) that ingest Dexcom data alongside other wearables.
Solutions 5
Packaged solutions the provider offers on top of the raw API surface.
Packaged solutions this provider offers.
Dexcom G7
Latest-generation 10-day all-in-one disposable CGM with the smallest, thinnest sensor and direct-to-watch streaming.
Dexcom G6
10-day CGM with separate transmitter and sensor; widely supported across partner integrations.
Dexcom ONE / ONE+
Simplified CGM tier targeted at intermittent CGM users in select markets.
Dexcom Stelo
Over-the-counter glucose biosensor for non-insulin users (US).
Clarity
Cloud reporting for patients and clinicians with AGP, time-in-range, and pattern recognition.
Resources
Every other property we hold for Dexcom — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/dexcom · machine-readable index on apis.io