help menu

Join us on the Community Forums!

  • Community Guidelines

    The Fitbit Community is a gathering place for real people who wish to exchange ideas, solutions, tips, techniques, and insight about the Fitbit products and services they love. By joining our Community, you agree to uphold these guidelines, so please take a moment to look them over.

  • Learn the Basics

    Check out our Frequently Asked Questions page for information on Community features, and tips to make the most of your time here.

  • Join the Community!

    Join an existing conversation, or start a new thread to ask your question. Creating your account is completely free, and takes about a minute.

Not finding your answer on the Community Forums?

Cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

How do I enable public OAuth access for my Fitbit developer app (no “Submit for Review” option )?

yesterday

yesterday

Hello,

I’m building a small iOS app, and I’m looking for guidance on how to enable public OAuth access for it.

What the app does

  • The app allows users to sync their Fitbit step count into Apple Health on iPhone

  • Currently steps only (read-only access)

  • No data is stored on servers — all processing happens on-device

  • The app uses OAuth 2.0 (Client) with a custom URL scheme redirect 

  • Default access type is Read Only

  • Intended for public distribution via the Apple App Store

Current issue

I have successfully registered the app on dev.fitbit.com, and OAuth works for my own Fitbit account. However:

  • I do not see any option to:

    • “Submit for Review”

    • Request public access

    • Change app status (private → public)

  • The app appears to be restricted to my developer account only

  • I’m concerned that non-developer Fitbit users (e.g., App Store reviewers) will not be able to authorize the app

I’ve checked both the main app page and Edit Application Settings, and I only see the standard OAuth configuration (Client ID, Secret, Redirect URL, scopes, etc.), but nothing related to app review or public access enablement.

What I’m trying to do

I’d like to:

  1. Submit this app for Fitbit review (if required), and

  2. Enable public OAuth access so that any Fitbit user can authorize the app

My question

What is the correct process to enable public access for an OAuth 2.0 client app if no “Submit for Review” option is shown in the developer dashboard?

If this needs to be handled manually by Fitbit, is there a specific form or contact I should use?

I’m happy to provide screenshots, app details, or additional context if needed.

Thanks very much for your help!

Best Answer
Labels:
0 Votes
0 REPLIES 0