POST with the changed record to every endpoint subscribed to that event for that property.2xx straight away, and processes the event afterwards.| Detail | Example |
|---|---|
| Your endpoint URL. It must use HTTPS | https://partner.example.com/wincloud/webhooks |
| The events you want | reservations.changed, rates.changed |
| The properties you integrate with | Your property IDs, for example international |
POST requests over HTTPS2xx once it has accepted the eventPOST with a JSON body and these headers:| Header | Value |
|---|---|
Content-Type | application/json |
X-RBS-Signature | t=<unix_seconds>,v1=<hex>. See Verify Webhook Signatures |
X-RBS-Event-Id | The event id, the same as id in the body |
X-RBS-Event-Type | The event type, for example reservations.changed |
X-RBS-Delivery-Id | A new identifier for each delivery attempt |
X-RBS-Attempt | The attempt number, starting at 1 |
data:{
"id": 4211,
"type": "reservations.changed",
"source": "WINCLOUD",
"customerCode": "international",
"customerName": "International Hotels",
"locationCode": "01",
"idempotencyKey": "international#...#10452#20261101144402000",
"createdAt": "2026-11-01T09:14:05.512+00:00",
"data": {}
}| Field | Type | Description |
|---|---|---|
id | integer | Unique event id. Use it to spot duplicates |
type | string | The event type |
source | string | The system that produced the event |
customerCode | string | The property ID, in lower case. It does not change, so use it to match events to a property |
customerName | string | The property's display name. It can change |
locationCode | string or null | The companyId within the property. null when the event applies to the whole property |
idempotencyKey | string | Identifies the exact version of the record this event describes. Treat it as an opaque string; its format can change |
createdAt | string | When WinCloud recorded the event, in ISO 8601 with a UTC offset |
data | object | The changed record. Its fields depend on type; see List of Webhook Events |
| Your endpoint replies | WinCloud |
|---|---|
2xx within 15 seconds | Counts the delivery as successful |
408, 429 or any 5xx, or no reply within 15 seconds, or the connection fails | Tries again later |
Anything else, including a redirect (3xx) | Stops. Redirects are not followed, so give the final URL |
id of each event you process and skip any you have seen. Do not use X-RBS-Delivery-Id for this; it changes on every attempt.data with the record you already hold, and keep the newer one.2xx as soon as the signature checks out, then do the work in the background, so you stay inside the 15 seconds.