help menu

Join us on the Community Forums!

  • Community Guidelines

    The Fitbit Community is a gathering place for real people who wish to exchange ideas, solutions, tips, techniques, and insight about the Fitbit products and services they love. By joining our Community, you agree to uphold these guidelines, so please take a moment to look them over.

  • Learn the Basics

    Check out our Frequently Asked Questions page for information on Community features, and tips to make the most of your time here.

  • Join the Community!

    Join an existing conversation, or start a new thread to ask your question. Creating your account is completely free, and takes about a minute.

Not finding your answer on the Community Forums?

Cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

sleep goal returns unexpected response

‎11-04-2017 08:48

‎11-04-2017 08:48

I followed the documentation for retrieving a user's sleep goal (v1.2) here: https://dev.fitbit.com/reference/web-api/sleep/#get-sleep-goal

 

Everything had previously been working fine using the resulting goal.minDuration field, but recently I found that one user is getting back a different response that doesn't match the documentation - it includes fields goal.bedtime and goal.wakeupTime and excludes the goal.minDuration field.  I would expect this change to require a new version of the sleep goal api since it is not additive/breaks the 1.2 contract.

 

Anyone else running into issues with this?

Best Answer
Labels:
0 Votes
0 REPLIES 0