timezone=UTC parameter not working as expected

[hippopotamus1]

Hello,

I'm having an issue with the timezone parameter when requesting intraday data.

Here is the API request I'm making:
/1/user/${userId}/activities/calories/date/YYYY-MM-DD/1d/1min.json?timezone=UTC

Even though I've specified timezone=UTC, the API still seems to return data in the user's local time, not UTC.

My understanding is that including this parameter should provide the data in UTC. Has anyone else encountered this, or am I misunderstanding how it works?

Any help would be greatly appreciated.

[GordonFitbit]

Hi @hippopotamus1 

I'm not able to reproduce this problem.   When I use "timezone=UTC" I see the data adjust for the UTC offset.

To test this problem, I looked at the output without the timezone offset enabled, and selected a unique calorie burn value during a time I was active (approx 8am local time).  Then reran the same query with the query parameter "timezone=UTC".  I notice the value at 8am has changed, and it's showing the calorie burn from 8am UTC.

For example, here is my calorie burn response at 7:35 am EST

When I use the timezone=UTC query parameter, the response at the same time is

If I look at UTC time (+5 hours), my response is

 Are you not seeing the same thing?