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: 

Your application has not been updated to access the Fitbit API via HTTPS

‎10-15-2014 17:36

‎10-15-2014 17:36

I received an email today saying that during the blackout test Fitbit has detected that my application has not been updated to access the Fitbit API via HTTPS.

We are using the Python fitbit library (https://github.com/orcasgit/python-fitbit) for all our apps, which I'm pretty sure uses HTTPS exclusively, so I'm confused by this email.

Do the subscription endpoints I create also need to be HTTPS?

Best Answer
Labels:
0 Votes
3 REPLIES 3

‎10-15-2014 17:55

‎10-15-2014 17:55

Hi Brad,

 

Subscription endpoints do not have to be HTTPS. We pulled access logs for yesterday and looked for all API requests that were made via HTTP.

 

Can you private message me with the Consumer Key of your application? I can double check for you.

Best Answer
0 Votes

‎10-16-2014 08:54

In response to SunsetRunner

‎10-16-2014 08:54

Thanks Dan, PM sent.

Best Answer
0 Votes

‎10-16-2014 17:34

In response to bradpitcher

‎10-16-2014 17:34

To verify if your application is making non-HTTPS requests to the Fitbit API:

  1. Go to http://httpschecker-30885.onmodulus.net/
  2. Enter your client key from https://dev.fitbit.com
  3. If your application had any non-HTTPS Fitbit API requests in the time period noted on the page, they will be displayed.
Best Answer