Garmin using Oauth 1.0.
Along with the usual implementations, the following needs to be considered -
A reportDeregistration endpoint (which marks user's authorized=false) is required for users who revoke access in their Garmin accounts.
We need to check the endDate of the user and past some time after that (eg - 14 days), we need to send a deregister request to Garmin API for the user. Otherwise, Garmin API will keep sending POST requests.
We also need to send a deregister request to Garmin API when a user is deleted to ensure that we don't receive any further POST requests from Garmin.
yatharthranjan
commented
3 years ago
Garmin using Oauth 1.0. Along with the usual implementations, the following needs to be considered -
reportDeregistrationendpoint (which marks user'sauthorized=false) is required for users who revoke access in their Garmin accounts.endDateof the user and past some time after that (eg - 14 days), we need to send a deregister request to Garmin API for the user. Otherwise, Garmin API will keep sending POST requests.