For the complete documentation index, see llms.txt. This page is also available as Markdown.

Webhooks

Webhooks allow partners to be notified when important events happen in Offers.

When one of those events are triggered, we will send an HTTP POST payload to the webhook's configured URL. Webhooks can be used to send a customer notification, initiate a policy renewal process or perform any custom logic.

To establish webhooks, partners can provide to their CSE:

1. Listener URL 2. Authentication Key & Secret 3. Support URL 4. Requested events (CSE may propose or suggest these as part of solutioning).

We will provide an HTTP signature generated on our end in Authorization header and the api key itself in X-Api-Key header. We will base the signature on your provided key pair. You can use the same HMAC based algorithm for signature verification, if required. Please use the information from the signature header to check which hash algorithm is used in order to validate the request. Currently, webhook requests are signed using sha256 algorithm.

In case of multiple failures with the webhook notification, where the partner supplied endpoint does not respond with a 200 OK, we will try the webhook for up to 3 times.

Authentication

Your webhook API endpoint should implement HMAC authentication to verify that the API request was sent and signed by Offers.

BOOKING_CREATED

Description: The payload is sent in a webhook to the Partner whenever the Offer is Confirmed through an API Request.

BOOKING_UPDATED

Description: The payload is sent to the Partner whenever the Confirmed Offer is Updated through an API Request

BOOKING_CANCELLED

Description: The payload is sent to the Partner whenever the Confirmed Offer is cancelled through an API Request

RENEWAL_CREATED

Description: Used to notify partner that the policy has been renewed.

Example:

RENEWAL_NOTIFICATION

Description: Used to notify partner about approaching renewal.

Example:

RENEWAL_DUE

Description: Sent on the renewal due date, the customer policy will be active until the end of the grace period (expiry_date).

Example:

RENEWAL_EXPIRED

Description: Sent on the renewal expiry date, the customer policy is no longer renewable after this event is triggered.

Example:

Last updated

Was this helpful?