12-20-2018 08:28
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

12-20-2018 08:28
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
I have a live web app which is synchronizing Fitbit data using OAuth2 and the Fitbit API. Currently, I have many active users who already registered their device with my web app and I am getting their device data through Fitbit API.
I now need to change the callback URL and the subscriber endpoint for the Fitbit API. I am concerned that it will affect the already registered users on my web app, and perhaps they'll need to reauthorize my web app to get their device data.
If I change the callback URL and subscriber endpoint on a live app, will it have any affect on my existing users?
Answered! Go to the Best Answer.
Accepted Solutions
01-03-2019 13:50
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



01-03-2019 13:50
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Hi @wli,
From the testing I have done, changing your callback URL and subscription URL will not revoke the token for your users. Therefore, your users should still be authorized to use your application. When changing the subscription URL, you will need to reverify the subscriberID.
Senior Technical Solutions Consultant
Fitbit Partner Engineering & Web API Support | Google

01-03-2019 13:50
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



01-03-2019 13:50
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Hi @wli,
From the testing I have done, changing your callback URL and subscription URL will not revoke the token for your users. Therefore, your users should still be authorized to use your application. When changing the subscription URL, you will need to reverify the subscriberID.
Senior Technical Solutions Consultant
Fitbit Partner Engineering & Web API Support | Google

