Updated documentation for the OAuth 2.0 authorization page `prompt` parameter is available here.
We've clarified the behavior of the `prompt` parameter. Previously, "prompt=login" would display both the sign in and app authorization page. Now, "prompt=login consent" (with a space, which will be URI encoded as %20) is required to request both the sign in and app authorization. "prompt=login" will require sign in, but only display the app authorization page if necessary. The app authorization page is not necessary when the person has already authorized the app with the same or fewer requested scope, the user has not revoked access to the app, and the authorization has not expired when using the Implicit Grant Flow.
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
Best Answer