api giving: Response code 500 (Internal Server Error) / Error id: A29EFF64:61D9_A92D826B:01BB_5A7CC3

[Fan3123]

I'm trying to grab data using the webAPI from Fitbit, but every time I try to export, this error is generated. 

You can see many others are having exactly the asme issue: https://github.com/NickHeiner/fitbit-export/issues/19

Can someone explain what's up with the Fitbit site/how to fix this?

{
  "message": "Response code 500 (Internal Server Error)",
  "host": "api.fitbit.com",
  "hostname": "api.fitbit.com",
  "method": "GET",
  "path": "/1/user/-/activities/minutesSedentary/date/today/max.json",
  "statusCode": 500,
  "statusMessage": "Internal Server Error",
  "requestUrl": "https://api.fitbit.com/1/user/-/activities/minutesSedentary/date/today/max.json",
  "responseBody": "{\"errors\":[{\"errorType\":\"request\",\"fieldName\":\"500\",\"message\":\"An error occurred with the Fitbit Web API while processing the request. Error id: A29EFF64:61D9_A92D826B:01BB_5A7CC3CF_CF63429F:35B9\"}],\"success\":false}"

HTTPError: Response code 500 (Internal Server Error)
    at stream.catch.then.e (\\100.82.76.16\volume-3-default\71e539140aab05178a3f\76b230477a3846258950e7edbb2d6695\site\wwwroot\node_modules\got\index.js:114:13)
    at wrappedPromise.linkTransaction (\\100.82.76.16\volume-3-default\71e539140aab05178a3f\76b230477a3846258950e7edbb2d6695\site\wwwroot\node_modules\newrelic\lib\instrumentation\core\globals.js:168:23)
    at wrappedPromise.wrapped [as __NR_wrapper] (\\100.82.76.16\volume-3-default\71e539140aab05178a3f\76b230477a3846258950e7edbb2d6695\site\wwwroot\node_modules\newrelic\lib\transaction\tracer\index.js:155:28)
    at wrappedHandler (\\100.82.76.16\volume-3-default\71e539140aab05178a3f\76b230477a3846258950e7edbb2d6695\site\wwwroot\node_modules\newrelic\lib\instrumentation\core\globals.js:202:26)
    at process._tickCallback (internal/process/next_tick.js:103:7)

[SiddhiFitbit]

Hi,

The reason you are seeing this error is `max` is not a supported value for time period. Valid values are: 1d, 7d, 30d, 1w, 1m, 3m, 6m, 1y as specified in https://dev.fitbit.com/build/reference/web-api/activity/

[Klinkehoffen]

Thanks very much: but who needs to fix this? Fitbit, or Nick? Then we can alert the correct person 🙂

[Gordon-C]

Since the Fitbit API doesn't support "max", the application would need to be changed.