08-06-2015 16:01
08-06-2015 16:01
1. Heart rate time series will now only include data points when Fitbit believes the device was being worn. This change affects all heart rate data ever captured by a Fitbit device. You might consider re-requesting heart rate data retrieved prior to July 25, 2015.
2. Your application should consider all numerical ids in the Fitbit API to be unsigned 64 bit integers. Many ids will cross the maximum 32 bit integer in the next couple of weeks.
3. OAuth 2.0 requests will be restricted to JSON and TCX formats. XML will no longer be supported with OAuth 2.0 requests starting August 17, 2015.
4. The custom logging endpoints (deprecated in October 2014) will be removed on August 27, 2015.
08-07-2015 04:03
08-07-2015 04:03
There is no chance to get the activity started on the device?
08-07-2015 11:36
08-07-2015 11:36
@freeubi wrote:
There is no chance to get the activity started on the device?
Not yet.
08-08-2015 11:57
08-08-2015 11:57
@JeremiahFitbit Does this mean that the body measurement section of the Fitbit web site will go away, and all historical data "lost" on 8/27? Or does this change just prevent third party apps from accessing the data?
08-11-2015 12:30
08-11-2015 12:30
Hello,
All measurements except fat and weight will be removed from API-Get-Body-Measurements (e.g. GET /1/user/-/body/date/2010-02-21.json) and API-Log-Body-Measurements
Can't really tell for sure, does that mean that since 27th of August 3rd party apps will not be ablte to POST weight and BMI data to a Fitbit body profile via /1/user/-/body/log/weight.json ? Or weight will still be allowed, but BMI will be calculated on Fitbit's side?
Thanks in advance.
08-11-2015 12:33
08-11-2015 12:33
Oh oh....I'm confused. I have a fitbit One with no heart rate etc. Does this mean that I won't be affected by the changes or will I need to make changes via script editor?
08-11-2015 12:39
08-11-2015 12:39
What's the reason for deprecating XML? It was the easiest to work with compared to JSON (at least I found). Any time I tried to parse out the JSON I got back it was always a pain in the ass..
08-11-2015 14:58
08-11-2015 14:58
@Michael wrote:
@JeremiahFitbit Does this mean that the body measurement section of the Fitbit web site will go away, and all historical data "lost" on 8/27? Or does this change just prevent third party apps from accessing the data?
@Michael: Please see the announcement at https://community.fitbit.com/t5/Fitbit-com-Dashboard/Old-manual-logging-pages-will-be-retired-on-8-2...
08-11-2015 14:59
08-11-2015 14:59
TimeWalker75a wrote:
Can't really tell for sure, does that mean that since 27th of August 3rd party apps will not be ablte to POST weight and BMI data to a Fitbit body profile via /1/user/-/body/log/weight.json ? Or weight will still be allowed, but BMI will be calculated on Fitbit's side?
@TimeWalker75a: BMI will still be available with weight and body fat percentage.
08-11-2015 15:05
08-11-2015 15:05
@TEvashkevich wrote:
What's the reason for deprecating XML?
@TEvashkevich: Over 95% of requests to the Fitbit API are for JSON. It's faster to parse, is easier to infer type, and is less verbose (which makes it smaller and faster to download).
We announced in October 2014 that all new API endpoints would be JSON only. We're now extending that to make all requests via OAuth 2.0 JSON only in order to phase out XML support.
08-11-2015 15:55
08-11-2015 15:55
Maybe I am just missing something, but what do you mean by the OAuth calls are going to switch from XML+JSON to JSON-only? OAuth calls are pretty much URL string driven, aren't they?
08-11-2015 16:08
08-11-2015 16:08
@EvanBasalik: If you make an API request using an OAuth 2.0 access token, the Fitbit API will only support a JSON response.
08-11-2015 16:12
08-11-2015 16:12
So, this functionally means that the XML variants of even the old APIs will no longer work? That's a pretty big breaking change.
08-11-2015 18:04
08-11-2015 18:04
Would OAuth 1.0 be decomissioned or still supported after August 27 ?
08-11-2015 18:27
08-11-2015 18:27
"Your application should consider all numerical ids in the Fitbit API to be unsigned 64 bit integers. Many ids will cross the maximum 32 bit integer in the next couple of weeks."
Can you please state an example of this in current api ?
Regards,
Aditya
08-11-2015 20:06
08-11-2015 20:06
Will Fitbit API still support OAuth 1.0?
08-11-2015 22:24
08-11-2015 22:24
08-12-2015 03:09
08-12-2015 03:09
For pure clarification.
I am using oAuth 1.0 , I am requesting everything as time series in JSON.
This will still work after August 17th ? , it's just I have three live apps and there is simply not enough time to get things through Apple.
Removal of oAuth 1.0 will need alot more notification to get apps updated
08-12-2015 08:12
08-12-2015 08:12
08-12-2015 08:25
08-12-2015 08:25
I would rather hear that from someone at Fitbit