Changes

Jump to navigation Jump to search

Setting/propertiesnotifyurl

1,083 bytes added, 11:39, 15 December 2023
no edit summary
A push notification (webhook) will be sent to this URL when a new booking, significant booking modification which effects availability , a guest message from OTA or cancellation occurs.
The bookid and status are appended to your url like this example.
<code>https://yoururl.com/yourpage?bookid=12345678&status=new</code>
Possible values for status are: new, modify, cancel, message
The card CVV can status modify could be included as a post variable sent for new or cancelled bookings if multiple fields are changed before the webhook sends, i.e. the URL contains 'cvvfirst webhook you receive may have the status =post' modify instead of new and is using https:The CVV will be sent one time onlya cancelled booking may have a webhook with status = modify, do not use status = modify reported by a webhook to assume anything about the status of the booking.
iThe card CVV and a token to retrieve it from the JSON getCard API function can be included as form url encoded POST data in the body of the push.e. your url
https<span style="color: #f3e504; font-size: 150%;" >{{#fas:lightbulb}} <//yoururl.com/yourpage?cvv=postspan> If you need to differentiate between multiple properties, an easy way is to include a property parameter in your URL
will be sent to the the following with CVV in post data<code>https://myserver.com/propid=1234 </code>
https://yoururlThe URL can contain template variables which will be exchanged with information from the booking.com/yourpage?cvv=post&bookid=12345678&status= Multiple URL's can be notified, enter each additional URL on a newline. Your server should return an HTTP 200 header to acknowledge receipt of the notify. If there is no response or a response HTTP code of 400 or higher the notify will be retried after a delay.
Outgoing messages are queued so there can be a short delay between the action occurring and the notification sending. The URL can contain template variables which status values are not synchronous, it is possible the first notification will be exchanged with information from have status modified or cancel instead of new if the bookinghas changed to that state before the message sends.

Navigation menu