Hey Everyone!
As you might noticed we have a busy time here at Fitbit working on the new
products and features for the last couple of months. We had a several big
days including Fitbit Ultra and Food Goal launches. Now it is the time for
the Fitbit API to catch up! We released several new API additions to support
those Fitbit products in the ecosystem. Some of them have been around for a
while, others are completely new and have been just released.
Let's jump to the list:
1) *Fitbit Ultra. Floors and elevation.* We have added the daily elevation
and floors resources tracked by Fitbit Ultra to the API. They are available
in the responses to Get-Activities calls as well as Get-Time-Series
resources. Please, note that these resources currently available only for
the users with a new version of tracker paired (though you could definitely
fetch floors and elevation from your friend or any public profile, who has
new Ultra).
Related links:
http://wiki.fitbit.com/display/API/API-Get-Activities
http://wiki.fitbit.com/display/API/API-Get-Time-Series
2) *Food Goal. *The Food Goal is a new way to manage your daily calorie
intake on the journey to the desired body weight. It is very dynamic and
based on your daily activities, so we decided it might be helpful to reveal
user's current food budget for the day in the API as well.
Related links:
http://wiki.fitbit.com/display/API/API-Get-Foods
And several other additions and improvements (some of them not so small!):
– We have added *sleep efficiency* to the sleep related calls and tracker's
*last sync time *to the Get-Devices endpoint.
(these two were entirely based on the developer community feedback –
thanks!)
– Support for fetching resources of other users from the user's social graph
is back for all of the Get-Time-Series
calls, so now you should be able to produce awesome graphs to compare
friend's activity trends over time.
– We extended activity and food logging, so now it is possible to create and
log *custom activities *as well
as food log entries without a reference to particular food in our
database. This could simplify the food logging
workflow and also great for writing *meal summaries *with all nutritional
details versus specific food entries to Fitbit.
– Some food tracking improvements here and there – calories field in
Search-Foods, new Get-Food endpoint
to request specific food details
(https://wiki.fitbit.com/display/API/API-Get-Food).
Thank you all for working with Fitbit API platform and looking forward for
your opinions about new features. Stay tuned!
– Pavel
--
Fitbit API documentation and resources: http://wiki.fitbit.com
Fitbit Developer's Portal: http://dev.fitbit.com/