Webhooks

You can edit webhooks in the application:

Read an example of using webhooks for a Slack integration here.

Webhook payload reference

Ondorse currently sends webhooks on these events

• Case created
• Case updated
• Case submitted
• Case review updated
• Case status of tasks execution updated
• Document created
• Document updated
• Document deleted
• Collect opened
• Collect closed
• Identity verification updated
• Portal notification created

Please note that this list is only a subset of events that are tracked by Ondorse.

Every event tracked by Ondorse can be used to send webhooks.

Therefore the list hereabove can be extended upon request.

👍

In order to help test configuration & connectivity during integration, Ondorse provides a test webhook

Whitelist of IPs

In order to make sure requests come from Ondorse's servers, you can whitelist this set of IPs.

15.188.136.142
35.180.82.98

Webhook Delivery & Retry Policy

Ondorse guarantees at least one delivery of every webhook event.

💡

Clients should implement idempotency using the event_id field to safely handle potential duplicate deliveries.

If your webhook endpoint:

• returns a non-2xx status code, or
• times out, Ondorse will automatically retry the delivery.

Retry Strategy

Ondorse uses exponential backoff:

• 1st retry: ~10 seconds after the initial attempt
• 2nd retry: ~20 seconds later
• 3rd retry: ~40 seconds later
• 4th retry: ~80 seconds later
• … doubling each time

Maximum delay: 4 hours (reached at the 12th retry)

Total Retry Duration

• Total retries: 15
• Approx. total delivery window: ~27 hours after the first attempt