You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 1, 2023. It is now read-only.
Hi all! Is there are an option to get field expires (like timestamp) instead of (or with) expires_in - to get token from Fitbit? If yes, would you please describe how to use expired field?
Some background
Our solution - client-server. Token uses expires_in value (as it is said in Fitbit documentation - link). Although our API (backend) requests us to use expires value for the token. Documentation or how-to work with expires (instead of expires_in) for the token in Fitbit we couldn't find. Any help would be highly appreciated.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi all! Is there are an option to get field expires (like timestamp) instead of (or with) expires_in - to get token from Fitbit? If yes, would you please describe how to use expired field?
Some background
Our solution - client-server. Token uses expires_in value (as it is said in Fitbit documentation - link). Although our API (backend) requests us to use expires value for the token. Documentation or how-to work with expires (instead of expires_in) for the token in Fitbit we couldn't find. Any help would be highly appreciated.
The text was updated successfully, but these errors were encountered: