Difference between revisions of "Setting/propertiesnotifyurl"
Markkinchin (talk | contribs) |
Markkinchin (talk | contribs) |
||
| Line 1: | Line 1: | ||
| − | A push notification will be sent to this URL when a new booking, significant booking modification which effects availability or cancellation occurs. | + | A push notification (webhook) will be sent to this URL when a new booking, significant booking modification which effects availability or cancellation occurs. |
The bookid and status are appended to your url like this example. | The bookid and status are appended to your url like this example. | ||
| Line 16: | Line 16: | ||
If there is no response or a response HTTP code of 400 or higher the notify will be retried after a delay. | 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 status values are not synchronous, it is possible the first notification will have status modified or cancel instead of new if the booking has changed to that state before the message sends. | ||
Revision as of 17:09, 9 April 2020
A push notification (webhook) will be sent to this URL when a new booking, significant booking modification which effects availability or cancellation occurs.
The bookid and status are appended to your url like this example.
https://yoururl.com/yourpage?bookid=12345678&status=new
Possible values for status are: new, modify, cancel
The 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.
The URL can contain template variables which will be exchanged with information from the booking.
Multiple URL's can be notified, enter each additional URL on a new line.
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 status values are not synchronous, it is possible the first notification will have status modified or cancel instead of new if the booking has changed to that state before the message sends.
