Skip to main content
Solved

Webhook question

  • August 27, 2024
  • 1 reply
  • 40 views

Forum|alt.badge.img+1

I had a situation where my APi webhooks were failing due to an expired certificate.  Unfortunately I was unable to fix it while I was away from my home due to some security measures I've implemented within the cloud.  

My question is do the webhooks stop sending to the endpoints after so many errors and if so how to get them working again?

Thanks for any suggestions

Best answer by ActivityFix

For each webhook event, if your server does not respond with status code 200 within 2 seconds, Strava will retry 2 more times (3 total) -- I am not sure what the interval on those retries is. After 3 failed attempts you will not receive a webhook event for that specific activity again. However, I don't think there is anything which will stop sending webhooks completely unless you unsubscribe. You should still receive webhooks for all new events.

See https://developers.strava.com/docs/webhooks/. Specifically

The subscription callback endpoint must acknowledge the POST of each new event with a status code of 200 OK within two seconds. Event pushes are retried (up to a total of three attempts) if a 200 is not returned. If your application needs to do more processing of the received information, it should do so asynchronously.
View original
Did this topic help you find an answer to your question?

1 reply

ActivityFix
Superuser
Forum|alt.badge.img+24
  • Superuser
  • 241 replies
  • Answer
  • August 27, 2024

For each webhook event, if your server does not respond with status code 200 within 2 seconds, Strava will retry 2 more times (3 total) -- I am not sure what the interval on those retries is. After 3 failed attempts you will not receive a webhook event for that specific activity again. However, I don't think there is anything which will stop sending webhooks completely unless you unsubscribe. You should still receive webhooks for all new events.

See https://developers.strava.com/docs/webhooks/. Specifically

The subscription callback endpoint must acknowledge the POST of each new event with a status code of 200 OK within two seconds. Event pushes are retried (up to a total of three attempts) if a 200 is not returned. If your application needs to do more processing of the received information, it should do so asynchronously.

Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept, you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings