Dexcom (G6 and older)

Connect legacy Dexcom G6 devices via the password-based integration, which requires users to enable Dexcom Share for data access.

dexcom is the provider slug for Dexcom (G6 and older).
For the OAuth-based dexcom_v3 integration, see Dexcom (OAuth based).

This provider is being phased out in favor of the new OAuth-based Dexcom integration. Consider migrating to the new API at your earliest convenience.

Enabling Dexcom Share

Your user needs to enable Dexcom Share for this connection to work:

1. Install Dexcom mobile app

   They must use the Dexcom G6 mobile app (iOS, Android).

   Note that the Dexcom Clarity app would not work for this integration.

2. Enable Dexcom Share

   Please refer to the official help article on how to enable Dexcom Share.

   They must have at least one follower^[1] on Dexcom Share to keep the sharing activated. Otherwise, the API would stop reporting data to Junction.

   ^[1] You can set up your own Dexcom account for your user to add as a follower in the Dexcom G6 mobile app. Alternatively, your user can invite [e-mail] as a follower.

3. Connect via Junction Link

   They must connect to Junction using their own Dexcom account — the one which their Dexcom G6 app is signed into. This should not be the account of a follower.

Junction Widget

To connect your device with the widget, follow the link wizard and enter your username and password.

Junction Link

You can also connect a Dexcom user to Junction using the Junction client. For additional information, please consult the API reference.

Python

link_token = client.Link.create(user_id)
client.Link.password_provider(
    link_token, "dexcom", username, password
)

Webhooks

On successful connection, you will receive a Connection created webhook. Daily webhooks daily.data.glucose.created and daily.data.glucose.updated will also be issued to your team as new or more up-to-date data becomes available during the day.

For this provider, however, Junction will begin to aggregate the data for the last 24 hours and will not go beyond that. As a result, there will be no Historical webhooks issued. If you would like to pull the data immediately after connection, you can use the user/refresh endpoint.