Detail level of IntraDay data, and timzone

[lsandini]

Hello,

The WebAPI docs specify the URI arguments that need to be passed when making a request for Intraday Heartrate data. The detail-level or granularity can be '1sec' or '1min', which is fine. Apparently other detail-levels are also supported, since I set mine to '5min' and it works fine.

https://dev.fitbit.com/build/reference/web-api/intraday/get-heartrate-intraday-by-interval/

On the contrary, the timezone can be passed as a Query Parameter, with only 'UTC' as an acceptable option. I tried others like 'EEST' or 'UTC+03', and the request was refused. The parameter is optional though, but with a single option it is useless.

Should the documentation be updated about the accepted 'detail-level' options ? Can we expect other timezone options in the future ?

Thanks,

Lorenzo

[JohnFitbit]

Hi @lsandini,

Welcome to the forums!

This is actually a great find. I tested the heart rate intraday endpoints using a 5min detail-level and confirmed I was able to get the data in 5 min intervals. I'm not actually sure if this supported or unsupported, but I can reach out to engineering to see if this is something we can add to our documentation or if this is unintended behavior.

In the meantime, I recommend checking out our Timezone documentation to see if the information there answers your question.

Let me know if you need anything else!

[lsandini]

Thanks John,

Just make sure they don't remove the 5min feature 😉

Lorenzo

[JohnFitbit · Accepted solution]

@lsandini After reaching out to engineering, they've confirmed that 5min and 15min is also supported. We'll update our documentation to reflect this information.

Thanks again for finding this!

[lsandini]

Very nice, thank you !

Just to make sure, I am wondering if there are similar granularity details that should be applied to Intraday Activity data. Currently only 1min and 15min are supported, but requesting 5min level of detail returns data too.

I am having an issue where requesting this 5min detail-level "steps" data every 15 min works perfectly all day, but crashes every night at 11 PM UTC, when I get an "error 500" from the WebAPI. I am being told that it could be due to requesting unsupported detail-level data, which of course could well be the case...