Webhooks

A webhook makes the platform call your endpoint when something happens, so you do not have to poll for changes. Visible to Admins only.

Columns

Column	What it shows
#	Row number in the current view.
Contract	The contract whose events this webhook receives.
URL	The endpoint that receives the callback.
Event type	The events subscribed to.
Status	Active or Inactive. Only active webhooks fire.

Create a webhook

1. Click Create.
2. Fill in the form.

Field	Required	Notes
Contract ID	Yes	Which contract's events to subscribe to. One webhook per contract; create several if you have several contracts.
Webhook URL	Yes	An HTTPS endpoint that accepts POST.
Event type	Yes	One or more events — see below.
Status	Yes	Active by default.

3. Click Create.

Event types

Event	Fires when
Order created	A new order is created — through the portal, the API or a widget.
Order item status changed	An order item changes status, for example when it is refunded.
Flight delay status	The status of a flight covered by a Delay Care booking changes, for example from Scheduled to Delayed.
Product added	A new product becomes available under the contract.
Product updated	An existing product's details change.
Product removed	A product is withdrawn from the contract.

You can select several events on one webhook.

Edit or delete

Click a row to edit it — the same form opens with the current values. Change what you need and save.

To delete, select the webhook using its checkbox and use the delete action.

warning

Deleted webhooks cannot be recovered. If you only want to pause delivery, set Status to Inactive instead — the configuration is kept and can be reactivated later.

Endpoint requirements

• Must be reachable over HTTPS.
• Must accept POST with a JSON body.
• Should respond quickly with a 2xx. Do the real work asynchronously.
• Should be idempotent — handle the same event arriving more than once without double-processing.

Payload formats are documented in Webhook integration.

Export

Download Excel exports the list, with the columns Contract, URL, Event type and Status. The file is named Webhooks_DDMMYYYY_HHMM.xlsx, for example Webhooks_26112025_1152.xlsx.