- « Previous
-
- 1
- 2
- Next »
05-10-2017 08:16 - edited 05-10-2017 09:37
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

05-10-2017 08:16 - edited 05-10-2017 09:37
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
We've started to receive a lot of API 500 errors beginning from around 18:30 UTC May 9th, this is an example:
An error occurred with the Fitbit Web API while processing the request.Error id: 6CA2F53A:41BC_A92D826B:01BB_5912095B_1ACF5886:432B
Nothing changed on our side since May 5th, so I'm guessing something's changed in the API?

09-18-2017 23:13
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

09-18-2017 23:13
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
Is there any solutions?
We are also facing the same issue, while getting sleep data
Service:
https://api.fitbit.com/1.2/user/-/sleep/date/2017-09-12/2017-09-19.json
Response
{"errors":[{"errorType":"request","fieldName":"500","message":"An error occurred with the Fitbit Web API while processing the request. Error id: A29E3252:4086_A92D826B:01BB_59C0B3AA_98533CB5:6416"}],"success":false}
09-22-2017 06:00
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

09-22-2017 06:00
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
We also get this error when we call this web service.
09-23-2017 04:43
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

SunsetRunner
09-23-2017 04:43
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
Come on Fitbit.
This is just a very small snapshot of today "23/09/2017".
[{"errorType":"request","fieldName":"500","message":"An error occurred with the Fitbit Web API while processing the request. Error id: A29E9A49:5AAF_A92D826B:01BB_59C60BAA_561CBD0D:6414"}]
[{"errorType":"request","fieldName":"500","message":"An error occurred with the Fitbit Web API while processing the request. Error id: A29E9A49:644D_A92D91CB:01BB_59C60D4E_56F60E05:24CA"}]
[{"errorType":"request","fieldName":"500","message":"An error occurred with the Fitbit Web API while processing the request. Error id: A29E261C:714D_A92D900A:01BB_59C61625_A89E6E1F:3674"}]
[{"errorType":"request","fieldName":"500","message":"An error occurred with the Fitbit Web API while processing the request. Error id: A29E261C:3AB3_A92D91CB:01BB_59C61A63_573557F7:24CA"}]
[{"errorType":"request","fieldName":"500","message":"An error occurred with the Fitbit Web API while processing the request. Error id: A29E261C:6F4D_A92D900A:01BB_59C61C88_A8AD4A6C:3674"}]
[{"errorType":"request","fieldName":"500","message":"An error occurred with the Fitbit Web API while processing the request. Error id: A29E261C:7ED9_A92D900A:01BB_59C61F68_562CE022:3673"}]
[{"errorType":"request","fieldName":"500","message":"An error occurred with the Fitbit Web API while processing the request. Error id: A29E261C:627B_A92D900A:01BB_59C62054_56313E9A:3673"}]
[{"errorType":"request","fieldName":"500","message":"An error occurred with the Fitbit Web API while processing the request. Error id: A29E261C:2B6B_A92D826B:01BB_59C62862_56A840E1:6414"}]
[{"errorType":"request","fieldName":"500","message":"An error occurred with the Fitbit Web API while processing the request. Error id: A29E261C:51B7_A92D91CB:01BB_59C633E9_57AEFECC:24CA"}]
[{"errorType":"request","fieldName":"500","message":"An error occurred with the Fitbit Web API while processing the request. Error id: A29E261C:4A51_A92D900A:01BB_59C6341E_568E2A4A:3673"}]
[{"errorType":"request","fieldName":"500","message":"An error occurred with the Fitbit Web API while processing the request. Error id: A29E261C:26C9_A92D91CB:01BB_59C63D14_AA6AB711:24C9"}]
[{"errorType":"request","fieldName":"500","message":"An error occurred with the Fitbit Web API while processing the request. Error id: A29E261C:8BF3_A92D826B:01BB_59C6412B_571F3377:6414"}]
10-05-2017 08:01
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

10-05-2017 08:01
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
@AndrewFitbit Any news about this issue?

10-05-2017 12:06
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



10-05-2017 12:06
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
We've deployed the fix for this issue and it should be resolved now. Let us know if you're still seeing issues.

10-06-2017 00:13
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

10-06-2017 00:13
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Thanks @DavidSFitbit for this great news!
I just come to have a look to our logs. Indeed, we did not get this error since 2017-10-03.

02-19-2020 04:19
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

02-19-2020 04:19
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Hi,

02-19-2020 11:02
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



02-19-2020 11:02
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Hi @RussellWS
Thank you for posting your question about the 500 errors. 500s errors are usually server or network issues which can be caused by various reasons (i.e. issues at Fitbit, issues within your infrastructure, etc.). In our documentation, https://dev.fitbit.com/build/reference/web-api/troubleshooting-guide/error-messages/#5xx-server-erro..., we suggest retrying your request again.
Last week, Fitbit did have several problems that generated 500 errors and we announced them on https://www.fitbitstatus.com/. We were able to isolate the problem and fix it.
If you're still receiving 500s, would please describe the issue in more detail.
Senior Technical Solutions Consultant
Fitbit Partner Engineering & Web API Support | Google

02-19-2020 19:57
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

02-19-2020 19:57
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Thank you for your response,
But still, we have the same issue for many users. It never happened before and we've confirmed that we have used valid credentials for the API calls.
From our end all we get the 500 code and the error message as a response.
Strangely the API call is working for our account (That's how we've confirmed that we passing valid credentials for the API call)
Please let us know, what kind of information that you need to resolve this error?
All we get the error ID which is different for each call
Here I'm sharing some of the messages with IDs which we have received yesterday
request: An error occurred with the Fitbit Web API while processing the request. Error id: 024296fffe17d2aa-0001f8f8-01217b88-c383d5637f76b7e8-72c4cc22-5.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 0242ecfffe00235c-000696e5-011dba83-cac37c3ed128d067-55ccb7cf-4.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 0242a4fffe75e206-00049154-0121cf33-f39a0f47785784f4-3e8edca5-10.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 024276fffe17581a-000210eb-011f32d7-4012899be377ea85-059df3e6-5.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 024215fffeb1d345-0004af95-0124f0a0-1154fbab5f490746-b0880ce9-5.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 0242c5fffe4c2aff-000370b3-013a5c6f-251254b51813b8e5-d95b5fef-13.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 0242defffea3a900-0004aa2e-013c885f-50c36ab8e056b2ef-56e2e715-29.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 0242d9fffeb33ec9-00048c68-013fe8e6-97d93e36d15a1d6b-d531b410-1.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 02429bfffed1bd58-0002efb9-014717eb-8fcbba8e9078b55b-c09d1562-15.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 024220fffe9674ed-000416a3-014598cf-e0a85c7be4c78db3-07e21b5e-3.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 0242effffea8ca4f-000470e1-014eeaa6-5bf0aeccbb34cbf3-1e579fca-23.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 0242bdfffe491e47-000376ef-014deec6-7d1ce04e0c15cd62-b95e1b5c-7.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 0242defffea3a900-0004aa2e-015c2f07-ffa18c1ced2f0f44-ab764ada-12.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 024220fffe973792-00044996-0169b85b-15f91dc1905ddef6-bdc55543-12.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 0242effffea8ca4f-000470e1-016ab6be-cf69b47ac144e54b-595d8334-18.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 0242defffea3a900-0004aa2e-0168735d-b89fd1d5de8ba95d-df49bd4b-38.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 0242d9fffeb33ec9-00048c68-016d1335-811ddcb4fbb22b7d-a8d9fd78-14.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 02421bfffe0248c0-00050b38-0170e02c-a552e64195804f27-e68e6fca-22.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 024202fffee46dde-0004953e-016cbe12-7a446895ebb19116-b8bf7d78-2.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 0242effffea8ca4f-000470e1-0170fdf7-c196fb46e5b7d851-67416785-12.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 024266fffe816a8a-0003887d-017d7946-dc2e703950088f12-064e3f29-47.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 024229fffe3b2f30-00042986-01756e33-88e8f147fbfe2cc1-7b7b560c-19.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 0242d2fffefe7287-0004420b-0176ac7b-e9f4dce077dc8b93-6ab4e0c0-13.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 024292fffeac0977-0004e4c1-017e440c-8f146a9a7dbe638a-73941af5-2.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 024215fffeb1d345-0004af95-0188da7d-0130cfde262fa7b6-3c9b53c8-3.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 024220fffe9674ed-000416a3-01878d50-5a6a872a8dcd8866-2d3657f3-26.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 0242ecfffe00235c-000696e5-018b5970-4eea85d2b8dbffe4-0821cc7f-8.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 024215fffeb1d345-0004af95-019036e2-48af43a03a9cedef-5093487a-15.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 024266fffe816a8a-0003887d-019a739f-e77356c34dfd417c-5977b2d6-18.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 02429bfffed1bd58-0002efb9-019376e5-e4b4ee9b04657299-6ad1f54e-48.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 0242cbfffe45d8e6-0005d5b6-01923214-8fb0e7744b45d225-f8e3e0f2-34.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 0242defffea3a900-0004aa2e-0190c678-7a19d94d40338bf1-cfea165e-5.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 0242bffffe85d42f-00040b6c-0195c7b8-a6179e1f8d0fd15f-8c259bb3-53.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 024244fffecb906c-00030447-019add7f-01ac2b32aa7c51ec-1af20bd7-8.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 0242ecfffe00235c-000696e5-01a249eb-142d190e032bc909-996f236b-6.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 024276fffe17581a-000210eb-01a34df3-ad9e785aded085f9-25d91ec0-28.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 02427bfffea0f501-0003bf97-01a9cbe9-021fef7e359be7c2-78ae6df2-58.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 0242a4fffe75e206-00049154-01af8052-b2ec13564f33319d-c3fdb85c-2.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 0242c5fffe4c2aff-000370b3-01aba504-ef428cc1b7096e61-8551cc31-31.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 024262fffe2c1bc6-000431e3-01af66b9-af9779cfbd09f5d9-88a97ba3-15.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 02427bfffea0f501-0003bf97-01b485b5-d7f42141b80e313a-254b210c-10.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 024240fffe9bc0c1-0004cd02-01d13abe-1c6313e7de8e0963-a9fca0a1-31.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 024244fffecb906c-00030447-01d453af-e7e961f868f285d7-d6d7f886-22.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 024296fffe17d2aa-0001f8f8-01d858f1-5b2d9c670ef1221d-971ee777-50.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 02428efffe4dd7a1-00046df1-01da3e2c-b31711ea6efb8793-f01a71be-9.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 024240fffe9bc0c1-0004cd02-01d9213e-591a7574a63cba7e-7140ad57-6.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 0242d2fffefe7287-0004420b-01e1352a-8a16074df7348250-97bc194f-5.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 0242a3fffea1ffb0-0004e1ee-01e364f4-e1179454fee892a7-9973eff9-28.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 024292fffe41cab7-0004cf7a-01e79477-a4cc949414242f36-a90f35a8-4.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 02424ffffe0d00b1-0004931a-01e7763c-5aa63a1fdfdb446c-c9c937fe-14.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 02420afffea8eece-0003e720-01e74731-73d98f3c541c4a11-0c29c9ea-35.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 0242ecfffe00235c-000696e5-01e7655f-07d47188963cfa2b-91236299-32.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 0242defffea3a900-0004aa2e-01e6d01b-59d71df26c3258c8-3bde3f22-3.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 02420dfffe42f478-0001dab4-01eccf9d-391c1e0a6463c80d-112a089a-3.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 02429bfffed1bd58-0002efb9-01eee357-5c34e2f0b9f8593e-fd4b892c-4.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 02429bfffed1bd58-0002efb9-01f9e03a-59796eea753be738-b4da0420-46.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 0242d2fffefe7287-0004420b-0208813e-fa388a2e89d4d93e-e70c0e97-3.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 024203fffe8861cf-0004ae81-020a45f8-518ec382ee8e05a0-f80ca857-8.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 0242c5fffe4c2aff-000370b3-02164f70-58221e3b651ae8ac-5e0ae27d-5.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 02421bfffe0248c0-00050b38-022cd29a-c0608b01636c1864-9d3cfce8-6.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 02429bfffed1bd58-0002efb9-022cecff-7aa6e9d08682ddbe-7c9d3429-13.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 024240fffe9bc0c1-0004cd02-0229e399-8918b9f8a8df04f8-9801f30d-24.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 024262fffe2c1bc6-000431e3-022cc9d6-978cc077381a16a4-675938d5-33.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 0242cbfffe45d8e6-0005d5b6-0233b9b2-201f8f10b06cfb41-b416b3ff-87.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 024262fffeaa3696-0003cbfc-0236add0-d92c670e8a691d62-3fa80c5d-31.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 0242bffffe85d42f-00040b6c-023da396-541c09dcf08549b0-f8beac7b-17.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 02420dfffe42f478-000c5c6a-0001fb57-b1e54d317ffbda38-fd40aeb2-5.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 0242fafffe511a3d-001180d5-0017bd21-a4f662f337176070-0373a080-7.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 024298fffe93ea1d-00193709-0038f619-9fea111201e4ae00-872dc30b-18.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 024205fffe11f91d-0011ba55-0039b4a6-2582229e1a54ff02-b16947de-45.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 024293fffeb19919-0011657e-003c001c-d85c7035aed2a411-78b811c9-7.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 0242a3fffea1ffb0-00188ffe-004806b1-b92d4319c877a3f2-7fc89cc9-14.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 024270fffe2d46a0-00145f20-00484024-b407a879bd146c4c-c39f36e9-34.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 024205fffe11f91d-0011ba55-004e29a6-72f8cf52e68382e1-83972e99-12.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 02428ffffe9cec5e-00138979-0051629e-552f290136882b92-9229ed34-5.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 024298fffe93ea1d-00193709-0053b4cc-59c9bda6be9313c2-202b9219-23.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 02426ffffe3cfb20-000fed07-005bfe21-5457d2cb528ef18f-54fcd791-20.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 02420dfffe42f478-000c5c6a-005e1de2-44eb78c0970c8cd5-8a9c5215-2.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 0242c6fffe16e420-000ea2ad-005ea2ab-14664f19746a70d6-fb238a6a-3.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 024220fffe973792-000fc14f-0063bad2-1988d398d2e63ea6-6da72385-17.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 024205fffe190da3-0014342c-0062b8c1-389c2cd96161d423-075ddbfc-40.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 02421efffeffd9b8-00138693-006d3f5b-705d5a7d7f8bff9c-4a3770c7-25.
request: An error occurred with the Fitbit Web API while processing the request. Error id: 024242fffee5990a-000fcc32-006e65c9-5432ded66303b804-b862a813-33.

02-20-2020 09:33
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



02-20-2020 09:33
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Hi @RussellWS
Would you please provide me with the API call you're executing that is generating the 500 error? Is this error occurring for some of your users or all of them?
Senior Technical Solutions Consultant
Fitbit Partner Engineering & Web API Support | Google

02-20-2020 09:55
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

02-20-2020 09:55
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Hi,
This error is occurring for several users. But working with our accounts.
Full API URL: https://api.fitbit.com/1/user/{USER_CODE}/activities/apiSubscriptions.json
Method: GET
Message: PHP Fatal error: Uncaught FitBitException: FitBitOAuth2::getSubscriptions: /1/user/{USER_CODE}/activities/apiSubscriptions.json: Fitbit request failed. Code: 500.

02-21-2020 15:34
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



02-21-2020 15:34
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
This issue was isolated and fixed. The 500 errors should be resolved.
Senior Technical Solutions Consultant
Fitbit Partner Engineering & Web API Support | Google


- « Previous
-
- 1
- 2
- Next »