Inventory Webhooks: Difference between revisions
Jump to navigation
Jump to search
Markkinchin (talk | contribs) |
Markkinchin (talk | contribs) |
||
| Line 1: | Line 1: | ||
== Web Hooks == | == Web Hooks == | ||
Send a web hook to your service whenever a room type needs syncing. | Send a web hook request to your service whenever a room type needs syncing. | ||
Enter the public facing URL to | Enter the public facing URL to receive the request. | ||
Optional headers can be specified for authentication or other purposes if required. | |||
The web hook request expects an HTTP response code between 200 and 299, if it does not see this it will be retried a number of times over the next 30 minutes before giving up. | |||
Web hooks are triggered by new bookings, modification to booked dates, cancellations, an inventory change or a price change on a room type. | Web hooks are triggered by new bookings, modification to booked dates, cancellations, an inventory change or a price change on a room type. | ||
| Line 10: | Line 14: | ||
The web hook request payload contains json data in | The web hook request payload contains json data in it's body with the roomId which triggered the request. | ||
This can be used to keep external services synchronised with minimum delay whenever changes occur. | This can be used to keep external services synchronised with minimum delay whenever changes occur. | ||