https://www.strava.com/oauth/deauthorize ?Thanks Nick,The problem is that i do not receive anything.Specifically i am looking for the de-authorization event but i am not receiving thisThis is my authorization link:
--You received this message because you are subscribed to a topic in the Google Groups "Strava API" group.To unsubscribe from this topic, visit https://groups.google.com/d/topic/strava-api/NjEQAnnWk_U/unsubscribe.To unsubscribe from this group and all its topics, send an email to strava-api+...@googlegroups.com.To view this discussion on the web visit https://groups.google.com/d/msgid/strava-api/bbbf9f91-795f-419f-8b40-22bbd2424546n%40googlegroups.com.
Hi nick,What i am trying to achieve is that if anybody deauthotizes my app from strava frontend, i get a mesaage (i assume a webhook) so that i can delete all his dataFrom the strava developer i shpuld grt an athlete - delete webhook. But i am testing this with no results.Webhooks are working fine for activities but not from webhooksThe de-auth would be an activity generated from my app but i would like to receive from stravaHope is clear.Thanks
--
Specifically, webhook events are pushed when an athlete revokes access to an application, or when an activity is created, deleted, or one of the following activity fields are updated
You received this message because you are subscribed to the Google Groups "Strava API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to strava-api+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/strava-api/CALXss_gLCq%2Bfo9fVZD9w6d_UNWmexjNSCjU5obJoLqgzFr2RUQ%40mail.gmail.com.
Hi Briant,
"The only time you will get the webhook for the athlete revoking access to your app is when the athlete goes to their settings page and clicks the "Revoke Access" button next to your app on the apps page. That is the only time this webhook is sent. "
This is exactly the message i am looking for and i am not receiving it.webhooks work for activities but not for this message (which i think is the most important).Is it a problem of "scope" in the auth request? I tried all sorts of combination with no luck