The WebHotelier booking engine can be launched from a hotel or other 3rd party website using simple links, complex links or HTML forms.
The easiest way to launch the booking engine is a simple link, e.g.:
<a href="https://example.reserve-online.net/">Book Online</a>
If you prefer your link to open the booking engine in a new browser tab, use the html attribute target="_blank":
<a href="https://example.reserve-online.net/" target="_blank">Book Online</a>
Unless otherwise noted, all HTTP requests should be GET/POSTed to the hotel's booking engine URL:
where [subdomain] replace with the subdomain assigned to each hotel.
For a full list of activated subdomains, you can visit the reserve-online.net.
Some properties may use their own custom domain & subdomain. Not all properties have a *.reserve-online.net subdomain.
All links/forms must target "https://". Non-secure links will still work but will cause a redirect before launching the booking engine. It's highly recommended to always point to the SSL version.
All booking engine links or forms can use one or more parameters as described below. The parameters can be mixed & matched where appropriate for more complex needs.
Used to automatically perform an availability request.
Set the preferred language.
Preset currency to display in availability results.
Switch to private rates via a booking code.
Enable a special offer using a voucher code.
Highlight a specific rate or special offer.
Retrieve and present a previously made booking.
Launch the booking engine in a specific view, e.g. maps.
Use the booking engine url to redirect back to the hotelier site.
Override session information, such as referer.
Redirect to any URL after creating a booking engine session (e.g. for booking source tracking).
Some API methods take optional or requisite parameters. A thing to keep in mind when making requests with parameters is that the WebHotelier API expects all data to be converted to UTF-8 and URL encoded. Sending data in any other encoding will result in garbage into WebHotelier. It wont be dangerous garbage (we will always store valid UTF-8) but it will still be garbage.