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.
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
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.
Best Answer
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
@JeremiahFitbit is there a notification list I can get on for when this feature comes out?
Best Answer
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
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.
Best Answer