Webhook Retry
Missed a webhook? Don't worry we got you covered!
There might be cases when a particular integrator fails to handle the webhook event, resulting in us getting a response status code other than 200 OK . In these cases, we will resend the webhook event again to the integrator after some fixed intervals of times that are mentioned in the table below
Retry count | Duration |
---|---|
1st | 10 seconds after the first event failed to return 200 OK status code |
2nd | 30 seconds after the 1st retry failed to return 200 OK status code |
3rd | 1 minute after the 2nd retry failed to return 200 OK status code |
4th | 10 minutes after the 3rd retry failed to return 200 OK status code |
5th | 30 minutes after the 4th retry failed to return 200 OK status code |
6th | 1 hour after the 5th retry failed to return 200 OK status code |
7th | 4 hours after the 6th retry failed to return 200 OK status code |
8th | 12 hours after the 7th retry failed to return 200 OK status code |
9th | 24 hours after the 8th retry failed to return 200 OK status code |
Fetching list of webhook events
You could also fetch the list of webhook events that were sent to your configured URL in case you missed something or want to cross verify events. Use the List webhook events API for the same.
For additional details you can also use the retrieve webhook event by id API.
Updated 20 days ago