08-30-2021 13:23 - edited 08-30-2021 15:03
08-30-2021 13:23 - edited 08-30-2021 15:03
As of ~3:45 PM today, our X-Fitbit-Signature logic is producing mismatches. Our API returns a 404 HTTP status code in this scenario (as instructed in the docs), which has resulted in our subscription endpoint being automatically disabled.
Nothing has changed on our end, so we're not sure if re-enabling subscriber endpoint makes sense. Has anything changed in the Fitbit API around this header validation that is recommended from the docs?
A quick response would be much appreciated!
Answered! Go to the Best Answer.
08-31-2021 15:37
08-31-2021 15:37
Hi @LifeOmic-Dev,
Sorry to hear that you're encountering issues with the X-Fitbit-Signature, and I'll be happy to take a closer look. To do so, could you submit a private support ticket through this form, then after the case is created, reply to the email with logs of the remote IP of the host sending the incorrect signatures that you're seeing, as well as the incoming signature and incoming message content.
Once the case has been created, I'll take over the case and communicate with you via email. Thanks!
08-31-2021 15:37
08-31-2021 15:37
Hi @LifeOmic-Dev,
Sorry to hear that you're encountering issues with the X-Fitbit-Signature, and I'll be happy to take a closer look. To do so, could you submit a private support ticket through this form, then after the case is created, reply to the email with logs of the remote IP of the host sending the incorrect signatures that you're seeing, as well as the incoming signature and incoming message content.
Once the case has been created, I'll take over the case and communicate with you via email. Thanks!