A webhook sends an event message to an address configured in another system. Expedia Group’s Rapid notifications use HTTP POST messages for booking events. This provides a travel example of receiving an update when something changes. Source: Expedia Group: booking notifications

A travel example

Suppose a supplier sends a cancellation event to an agency system. A useful workflow would match it to the correct booking, update the record and flag any action for the adviser. This is an illustrative design, not a claim about a specific Travelgenix connection.

Delivery needs checking

Stripe’s webhook guidance tells implementers to verify signatures and account for duplicate events. Use those as questions for any proposed connection: how does it check the sender, recognise a repeated notification and recover a missed update? Follow the actual provider’s rules rather than copying another service’s settings. Source: Stripe: webhooks

What to test

Ask for a demonstration in which the receiving system is briefly unavailable. Check whether the update is retried, whether the team can see the problem and how the stored booking is reconciled afterwards. A sent notification and a successfully processed update should be separately visible in your test evidence.

Written and updated by Travelgenix. Sources checked on 16 October 2026. Worked examples and checklists are editorial illustrations and recommendations, not customer results.