You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have played around a bit with the "new" dexcom share API and wanted to share some findings real quick.
The lagacy Dexcom Share API we all have been using will get deprecated, according to "unoffical sources". Nobody knows when that will happen but when it does, all Dexcom integrations will stop working. Since it is not an officially supported API, Dexcom can switch it off whenever they want, without communicating in advance. Not good.
The "new" API (docs here: [https://developer.dexcom.com/docs/]) is based on oAuth so won't be possible to reverse engineer the same way as with the legacy API (unless you get hold of a valid client secret). It says in the doc that it does not provide real time data but I strongly believe it does. Garmin uses this API for their dexcom apps and they provide real-time data. Also, when I applied for a dev account they specifically asked me if I needed real-time data or not.
So I made a quick test and manage to run a successful auth and fetch towards their sandbox environment. Access to production requires a production dev account, which I didn't get (you need to go through their enrolment process and answer lots of questions). It seems they are pretty restrictive on who they assign production access to. Bummer but understandable I guess.
it would be interesting to know if aynone here managed to get access to their production environment for real-time data access.
I'd be happy to share more details if aynone is interested, just reach out to me.
//Fredrik
The text was updated successfully, but these errors were encountered:
I have played around a bit with the "new" dexcom share API and wanted to share some findings real quick.
The lagacy Dexcom Share API we all have been using will get deprecated, according to "unoffical sources". Nobody knows when that will happen but when it does, all Dexcom integrations will stop working. Since it is not an officially supported API, Dexcom can switch it off whenever they want, without communicating in advance. Not good.
The "new" API (docs here: [https://developer.dexcom.com/docs/]) is based on oAuth so won't be possible to reverse engineer the same way as with the legacy API (unless you get hold of a valid client secret). It says in the doc that it does not provide real time data but I strongly believe it does. Garmin uses this API for their dexcom apps and they provide real-time data. Also, when I applied for a dev account they specifically asked me if I needed real-time data or not.
So I made a quick test and manage to run a successful auth and fetch towards their sandbox environment. Access to production requires a production dev account, which I didn't get (you need to go through their enrolment process and answer lots of questions). It seems they are pretty restrictive on who they assign production access to. Bummer but understandable I guess.
it would be interesting to know if aynone here managed to get access to their production environment for real-time data access.
I'd be happy to share more details if aynone is interested, just reach out to me.
//Fredrik
The text was updated successfully, but these errors were encountered: