05-19-2021 10:27
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

05-19-2021 10:27
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
I am trying to integrate fitbit with a mobile app. The app redirects the user to a web browser where they access the fitbit authorization page and select the permissions they would like to allow. From here the redirect_uri is set to an endpoint running on my server that gets hit and returns a friendly message to the browser. However, I need someway to redirect the user back to the mobile app once the endpoint returns successfully. How should I implement oauth2.0 for a mobile app as opposed to a web app? How do I get the user back to the app instead of just showing the browser?

06-02-2021 12:50
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



06-02-2021 12:50
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Hi @dever_node1
Maybe there are a few mobile developers on here that can provide some recommendations. It might make sense to have the user redirect to your mobile application, then have the mobile application communicate with the server. Another option is you may specify multiple redirect URLs in your application registration at dev.fitbit.com but the redirection will not be sequential.
Gordon
Senior Technical Solutions Consultant
Fitbit Partner Engineering & Web API Support | Google

