Sync Updates (Webhooks)

Configure webhooks to receive real-time updates from ZealConnect directly into your system.

Configuration

Please contact our Support Team at support@zealconnect.com and provide:

Endpoint URL — The HTTPS URL on your server to receive webhook events

Once received, our team will configure the webhook and confirm when events are live.

Your webhook endpoint must be publicly accessible over HTTPS with a valid SSL certificate.

Request Requirements

Your endpoint must support an HTTP POST method to receive webhook events.
This allows ZealConnect to send event data to your system.

Response Requirements

Your endpoint must return an HTTP 200 OK response upon successfully receiving
the webhook event. This confirms to ZealConnect that the event was delivered.

Retry Policy

If your endpoint does not return a 200 response, ZealConnect will automatically
retry the event up to 3 times. If all retry attempts fail, the event will be
skipped and no further delivery will be attempted.

Attempt	Behaviour
1st	Initial delivery
2nd	Retry if no 200 response received
3rd	Retry if no 200 response received
4th	Final retry if no 200 response received
After 4th	Event is skipped. No further attempts are made.

Important: Ensure your endpoint responds with HTTP 200 as quickly as possible.
If processing takes time, acknowledge receipt immediately and handle the
event asynchronously to avoid unnecessary retries.

Webhook Events

ZealConnect sends webhook events using a standard structure:

{
  "EventId": "string",
  "EventType": "string",
  "Timestamp": "date-time",
  "Data": { }
}

ZealConnect sends two types of webhook events:

Event	Trigger
`BOOKING_CONFIRMED`	Hotel has confirmed the booking — HCN is available
`BOOKING_ESCALATED`	Booking requires intervention from client due to discrepancy

BOOKING_CONFIRMED

Triggered when ZealConnect successfully reconfirms a booking:

{
  "EventId": "01KMG1RHBY50ZJ9M36D87THWBE",
  "EventType": "BOOKING_CONFIRMED",
  "Timestamp": "2024-03-15T14:30:00Z",
  "Data": {
    "BookingId": "BK-00123456#123",
    "BookingCode": "BK-00123456",
    "LineCode": "123",
    "PointOfContact":{
        "Name": "Sarah Johnson",
        "Department": "Reservations",
        "PhoneNumber": "+1-555-0123",
        "Email": "hotel@outlook.com",
    },
    "HotelConfirmationNo": "HCN-2024-8892",
    "Channel": "HOTEL_CALL",
    "CheckInInstructions": "Guest requested late check-in approved"
  }
}

Webhook Payload Fields

Field	Type	Description
BookingId	`string`	Unique booking identifier in the format `BookingCode#LineCode`.
BookingCode	`string`	Primary booking reference provided by the client.
LineCode	`string`	Sub-booking or line-level identifier provided by the client.
PointOfContact	`object`	Details of the person at the supplier or hotel responsible for handling this booking.
PointOfContact.Name	`string`	Full name of the point of contact who handled the booking at the supplier/hotel.
PointOfContact.Department	`string`	Department of the point of contact (e.g., `Reservations`, `Front Desk`).
PointOfContact.PhoneNumber	`string`	Contact phone number of the point of contact, including country code if applicable.
PointOfContact.Email	`string`	Email address of the point of contact.
HotelConfirmationNo	`string`	Confirmation number provided by the supplier or hotel. If multiple, values will be separated by `
Channel	`string`	Source of the update (e.g., `HOTEL_CALL`, `SUPPLIER_EMAIL`).
CheckInInstructions	`string`	Additional instructions, notes, or special requests related to check-in.

BOOKING_ESCALATED

Triggered when a booking cannot be confirmed and requires client to intervene:

{
  "EventId": "01KMG2PKH6D87THWBENGF2S4KP",
  "EventType": "BOOKING_ESCALATED",
  "Timestamp": "2024-03-15T10:00:00Z",
  "Data": {
    "BookingId": "BK-00123456#123",
    "BookingCode": "BK-00123456",
    "LineCode": "123",
    "Reason": "Issue found - Discrepancy in Travel Date",
    "Remark": "We Initially called the hotel to reconfirm this booking; however, they were unable to locate the reservation under the guest name. Then coordinated with the supplier to obtain the HCN. After receiving the HCN,we contacted the hotel again and spoke with the front desk agent. She advised that under HCN: (HCN-NO), the reservation is scheduled from 29 March to 31 March 2026 for 2 nights. However, as per our records, the booking is scheduled from 27 March to 31 March 2026 for 4 nights. To resolve this discrepancy, contacted the supplier again. They responded by stating: “Please inform your guest that everything is fine as this booking is a normal one, so there is no need to worry about check-in.” For re-verification, we called the hotel once more and spoke with try from the front desk. He informed that the date discrepancy is still not resolved in their system."
  }
}

Field	Type	Description
BookingId	`string`	Booking identifier i.e. BookingCode#LineCode.
BookingCode	`string`	Booking Code Provided By Client.
LineCode	`string`	Line Code Provided By Client.
Reason	`string`	Reason for escalation (e.g., Issue found - Discrepancy in Travel Date).
Remark	`string`	Additional notes or context about the escalation.

Configuration#

Request Requirements#

Response Requirements#

Retry Policy#

Webhook Events#

BOOKING_CONFIRMED#

Webhook Payload Fields#

BOOKING_ESCALATED#