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: 

Subscriber verify with Ngrok not working properly.

‎04-18-2022 04:34

‎04-18-2022 04:34

Hello,

 

I am using ngrok to test the subscription functionality, and despite responding as the docs say I should (204, 404) the endpoint will not verify. What should I do?

 

Connections ttl opn rt1 rt5 p50 p90
12 0 0.00 0.01 5.00 5.01

HTTP Requests
-------------

GET /fitbit 204 No Content
GET /fitbit 404 Not Found

Best Answer
0 Votes
2 REPLIES 2

‎04-18-2022 04:58

‎04-18-2022 04:58

OAUTH id: 237ZXH

Best Answer
0 Votes

‎04-19-2022 08:15

‎04-19-2022 08:15

After actually deploying the API, I have concluded that Fitbit does not support Ngrok for the local development of subscribers. Definitely think this would be a good thing to support though, as not everyone can afford to test these things live

Best Answer
0 Votes