Moving from polling to webhook

[HankZ]

We are planning for the implementation of the web hook subscription.
A few questions pop up:

1. in the https://www.strava.com/settings/api page: Do we need to change the authorization callback domain?

2. Do our users to reconnect our app to Strava?

3. Does a manual exsist that guides us from the current way of polling for results to the new webhook system?

Our preference is that the users will not experience any negative issues only positive such as a quicker response after a training session. 

Any help is welcome.

[ActivityFix]

1. No, not unless you're changing the site URL
2. No, webhooks are independent. You will get webhooks for relevant events instead of having to poll for them. Which events you receive will depend on permissions the athlete authorized (e.g. you won't get a webhook for a private activity if they haven't given activity:read_all)
3. https://developers.strava.com/docs/webhooks/ - There isn't really a manual for going from polling to webhooks. Instead of polling, you'll get a webhook for every event and you can act on that if you want to. aspect_type will tell you what kind of event it is. If you only care about new activities, for example, you can ignore anything which isn't "create". There is also a node.js example @ https://developers.strava.com/docs/webhookexample/