06-09-2015 09:30
06-09-2015 09:30
I'm trying to develop a Python script that pulls my data down periodically (daily) for offline analysis, and discovered that the OAuth 2.0 refresh_token is usable only once. Since I'm only making API calls once a day, my access_token will always be expired, requiring a refresh call. I don't want to have to save a new refresh_token each time I make an API call, I just want to refresh my existing token. Are there plans to provide permanent access_token's or refresh_token's for the OAuth 2.0 API? If so, will this be done during the beta cycle, or only after OAuth2.0 goes out of beta? If not, how can I make repeated once-daily calls to the API using OAuth 2.0 (for heartrate retrieval) without having to save an update refresh_token each time?
Answered! Go to the Best Answer.
06-09-2015 10:58
06-09-2015 10:58
We will email all app owners when OAuth 2.0 is out of beta. We regularly post announcements to this forum and pin them to the top of the page.
06-09-2015 10:45
06-09-2015 10:45
Hi @jwbernin, yes, we do have plans to add a special type of authentication for this scenario in the coming months.
06-09-2015 10:54
06-09-2015 10:54
@JeremiahFitbit is there a notification list I can get on for when this feature comes out?
06-09-2015 10:58
06-09-2015 10:58
We will email all app owners when OAuth 2.0 is out of beta. We regularly post announcements to this forum and pin them to the top of the page.
03-18-2016 06:03
03-18-2016 06:03
Any update? This sounds like what I need.
03-18-2016 06:03
03-18-2016 06:03
I was referring to: Hi @jwbernin, yes, we do have plans to add a special type of authentication for this scenario in the coming months.