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: 

FitBit Security Department blaming Warranty Fraud on 3rd party app

‎09-21-2017 05:41

‎09-21-2017 05:41

We have a user who is using Fitbit's API to connect to our app.  It appears someone changed their email address at Fitbit in, as Fitbit Security said, "the hopes of committing Warranty Fraud".

 

When our user contacted Fitbit Security Department they said "this sometimes happens when a 3rd party is added access, so maybe your tech guy can do something to better secure the accounts?."

 

What is this?  How does our app's reading of steps (which are sent from Fitbit to our app) cause Fraud and/or the changing of a user's account?

 

Is there documentation of best practices for preventing this?

 

Thanks

 

 

Best Answer
0 Votes
1 REPLY 1

‎09-21-2017 09:30

‎09-21-2017 09:30

This might get better replies from the API board. If I had to guess maybe you're client secret token is exposed?

 

Further reading on OAuth

 

Honestly I'm just guessing, I'm waiting for my Ionic to come in before I actually try my hand at FB development.

Best Answer
0 Votes