Glucose API

Add to the public available API endpoints an endpoint to be able to create, read, update and delete glucose readings
4 Comments
Status changed to: Reviewed By Moderator
LizzyFitbit
Premium User
Fitbit Moderator
Fitbit Moderator

Hi @TrevorT1962, and thanks for taking the time to share this suggestion about adding Glucose to our Web API with us. We rely on feedback like yours to help us develop products and features that we know our community wants to see. If this suggestion receives votes from other customers and gains popularity, it will be shared internally with various teams at Fitbit. To learn more about how Fitbit decides which suggestions get developed, visit our FAQs.

Watch this space for status updates. In the meantime, try visiting Health & Wellness to talk with other members about all things health and fitness.

SunsetRunner
Not applicable

Hello @TrevorT1962 ,

thanks a lot for your suggestion. I understand, and indeed I checked the webapi documentation, that the API to integrate glucose measures is not available by Fitbit.

 

@LizzyFitbit Based on your reply may I suggest to revise and reopen the following suggestions that have been locked with an evident wrong reason by @YojanaFitbit ? Thanks a lot.

 

 

https://community.fitbit.com/t5/Feature-Suggestions/Option-to-connect-with-LibreLink-App-glucose-rea...

 

https://community.fitbit.com/t5/Feature-Suggestions/Continuous-Blood-Glucose-Monitoring-with-Medtron...

 

https://community.fitbit.com/t5/Feature-Suggestions/Integration-of-MySugr-App-for-diabetes-and-blood...

 

https://community.fitbit.com/t5/Feature-Suggestions/Fitbit-Sense-smartwatch-and-MiaoMiao/idi-p/45009...

 

rilhia
Jogger

@LizzyFitbit I manage a tech community and one of the most frustrating issues we've found our users talking about is the requirement for "many votes" before anything is taken seriously. People tend to come to communities for specific reasons. They don't generally look at everything to help assess the legitimacy of a request. That is your job.

Now, on the glucose API. I am more than capable of using your APIs. I have actually used them to demonstrate uses for tech that might engage developers before. I am a type 1 Diabetic and would like to make use of the glucose tracking. But I already have an app for this. I use the Freestyle Libre. For me to get a result and then have to manually add that to FitBit is utterly ridiculous. To the point of making the glucose tracking in your app pointless. However, I saw the posts referenced above and went to look at the API. I didn't recall seeing the ability to add my glucose results via the API, but I thought I would look. It is not there. I could very easily knock something up to do this so that I do not need to remember to manually add my glucose. But since the functionality is not there, I can't. Since I can't, I won't use it. It's as simple as that.

So, I will "vote" for this, which'll take this up to 10 votes. Do you think that ONLY 10 people would benefit and make use of the glucose feature if this was added? I think we both know that is not the case. So please speak to the product manager who deals with the API and get them to open this up. It should be a small piece of work and will open up this feature of your app to SO MANY people.

miketheman
Jogger

I'll agree here - in absence of a rich partner integration ecosystem, users are beholden to using the only interfaces available to us, and in the glucose realm, there's only one integrated ecosystem, and it's not with the vendors I use.

Instead of waiting for partner relationships to be developed, why not open up the API for end users to build their own integration, at the very least until a partner integration exists.

To comment, you must first accept the terms of the Idea and Feedback Submission policy.