Getting 500 Error on Activities Endpoint

[Jeff_New_Ocean]

We have been receiving 500-Internal Server Error from the GET activities endpoint for all requests since 17:20 UTC today.

Example request:

https://api.fitbit.com/1/user/63P6S9/activities/date/yyyy-mm-dd.json

Response:

{
"error":{
"code":500,
"message":"Internal error encountered.",
"status":"INTERNAL"
}
}

Can you please assist?

Thanks,
Jeff Humphry

[xivind]

I am experiencing exactly the same problem with the GET activities endpoint for all request as of today. It seems like the https://status.fitbit.com/ has no incidents regarding this. But the error code suggests this is a server side issue. Please help 🙂 

[bickster]

So are we. We are getting more support tickets then we can handle at the moment. @JohnFitbit mentioned that Fitbit is aware of the issue.

[Hielko]

As far as we can see, the GET/POST activities 500 issue has been resolved now. On our test devices it is working again, and no new reports issues by users of our app.

[Hielko]

Sadly, the problem is back: again the 500 response with the POST activity (didn't test the GET activity now).

[Jeff_New_Ocean]

I have been getting good responses from the GET activity now since today 12:52 UTC (8:52 AM ET).

[Hielko]

On our test devices it still doesn't work (13:38 UTC). Yesterday we had a situation that it worked on one phone and not another phone (later it didn't work on both phones). Really weird what is going on. 

[xivind]

I am still struggling with the 500 error. Is it resolved for you guys still @Jeff_New_Ocean @Hielko @bickster  ?

[Jeff_New_Ocean]

Hi @xivind, from our perspective it has been resolved since last Wednesday at 19:26 UTC. Note that we only call GET https://api.fitbit.com/1/user/[userId]/activities/date/yyyy-mm-dd.json

[Hielko]

If you use POST activity requests, you can check our post with an explanation when you get the 500 response, and what the workaround is: https://community.fitbit.com/t5/Web-API-Development/same-activity-upload-for-some-users-response-500...

[bickster]

Nope. We are still struggling as well. @Hielko suggested a couple request changes we could make that seem to work. We might try those.