02-24-2021 13:51
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

02-24-2021 13:51
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
The subscription verification for our new app is failing.
The endpoint is visible to the outside world, and it is actually returning the correct 204/404 replies when the code is either correct or invalid (going directly to the site and entering in the ?verify=<key> works correctly and responds with the correct status code).
However, hitting the verify button on the Fitbit side...it never actually verifies.
02-26-2021 11:11
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



02-26-2021 11:11
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Hi @dxhans5
Would you please private message me your client ID and subscriber ID? I'll see if I can find additional information in our logs.
Gordon
Senior Technical Solutions Consultant
Fitbit Partner Engineering & Web API Support | Google

02-26-2021 11:23
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

02-26-2021 11:23
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Thank you for getting back to me.
OAuth 2.0 Client ID
22C45P
SubscriberID
https://sync.walkertracker.com/api/callbacks/fitbit.php

03-03-2021 10:12
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

03-03-2021 10:12
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Hi Gordon.
Thank you for getting back to me.
OAuth 2.0 Client ID
22C45P
SubscriberID
https://sync.walkertracker.com/api/callbacks/fitbit.php

03-04-2021 16:02
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

03-04-2021 16:02
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
@Gordon-C I was wondering if there were any updates on this?

