Strava webhooks

[aaron-schroeder]

To me, this is the logical complement to bulk-importing strava activities. Theoretically, the two features would allow the user to save all their activities, past and future, without having to do anything manually.

Celery seems like a good solution to handle the tasks of reacting to webhook events, freeing up the server to respond to the strava request in a timely manner.

It makes sense to add a page where webhook subscriptions were viewable.

Notes

• From strava api docs: 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:
  • Title
  • Type
  • Privacy, requires an access token with activity:read_all scope

References

• https://developers.strava.com/docs/webhooks/
• https://stravalib.readthedocs.io/en/latest/reference/client.html#subscription-related-methods