lukasolson/fitbit-node

Issues

• Listing the default endpoint version = 1.2 is misleading.

  #32 opened 2 years ago by gordoncrenshaw
  1

• use different callbacks via Authorization flow

  #31 opened 4 years ago by RayDeanTech
  0

• Is redirectURL is mandatory for getAccessToken(code, redirectUrl) function ?

  #30 opened 4 years ago by gbharath5182
  2

• Is redirectURL is mandatory for getAccessToken(code, redirectUrl) function ? because we are doing Authorize from Mobile APP and getting tokens in backend (NODE JS).

  #29 opened 5 years ago by gbharath5182
  0

• Version 2.2.0 is not published to NPM

  #28 opened 5 years ago by Francis-Ouellet
  1

• allow non-user dependent requests

  #26 opened 7 years ago by xxzefgh
  6

• Post call does not follow promise catch convention upon error?

  #19 opened 7 years ago by cdichiara
  2

• Deprecated Promise rejection warning

  #25 opened 7 years ago by kennymark
  2

• refreshAccessToken does nothing

  #18 opened 7 years ago by handsingroup
  3

• Fitbit API 1.0 is too old (for example no sleep stages)

  #17 opened 7 years ago by haraldronge
  1

• yall didn't publish 2.1.0 version to npm

  #24 opened 7 years ago by imkimchi
  1

• Keep running into Fitbit error message "insufficient_permissions"

  #16 opened 7 years ago by ericvrp
  1

• Can't get getAccessToken working

  #15 opened 7 years ago by ericvrp
  3

• "Bad Request" for refreshAccessToken

  #14 opened 7 years ago by nurseybushc
  1

• How about revoking the access to the application?

  #9 opened 8 years ago by ShrujanKotturi
  5

• calling getRefreshToken throws a 400 error

  #7 opened 8 years ago by ldeluca
  1

• Push version to NPM?

  #5 opened 9 years ago by abeaclark
  1

• Add OAuth2 support

  #3 opened 9 years ago by pplewa
  3

• Allow sending body within PUT/POST requests

  #2 opened 9 years ago by lukasolson
  1

• requestResource not resolving

  #1 opened 9 years ago by danielst-vccp
  2