If you do not have an account on HomeAway:
If you do have an account on HomeAway:
Proceed with Step 2
Step 2
Our booking engine can fully integrate with your WordPress website using our plugin.
Plugin is available for download here.
Steps:
Insert following shortcode.
[webbookingpro hotelid="xxx" language="en|de|it|sl|sr|hr|es" currency="EUR" showlogo="1|0" showfooter="1|0" darktheme="1|0"]
only hotelid is required. If you have multiple properties you can combine ids
4. Now click on "Map Rooms" under AirBnB line.
5. For each room copy from WebBookingPro a calendar link.
6. Now Login to your Airbnb Account
If you already have an Airbnb account, click here to access it: www.airbnb.com
Click Save Changes
Repeat the steps above for ALL of your Airbnb rooms you'd like to sync with WebBookingPro.
On WebBookingPro, click Import once completed - Your channel is now live!
Please take the following considerations in mind when working with a calendar channel such as Airbnb:
Many OTA portals can use iCAL for real-time availability checking - Air B&B, Vrbo (Homeaway), FlipKey, 9Flats, ...
Calendar channels, otherwise known as Vacation Rental Sites, have become very popular in recent years as the typical traveler has become more internet savvy. These channels provide travelers with many options, from renting low cost bedrooms to booking stays at palatial estates. These channels have tapped into the public's desire to stay in "real" places away from tourist areas.
If your property is not marketed correctly, calendar channels can become a real competitive threat. Thankfully, WebBookingPro has you covered as we can integrate with any calendar channel that uses the standard iCal format.
With a typical channel (such as with booking.com od Agoda), WebBookingPro has a direct connection where we can send many values, such as:
Calendar-based channels work differently from those channels. With calendar channels, we provide them with a special calendar file that contains "appointments". This is similar to placing an appointment on your personal calendar, but in this case, the appointments lasts an entire night. Dates that are not booked are "empty", so they remain Available for booking.
With Calendar channels, WebBookingPro can only send Availability with support for Closed dates. All other values must be set directly in the channel's extranet, such as:
Your availability is constantly updated based on the reservations and other data that is sent to WebBookingPro. With this information, WebBookingPro updates the calendar file in real-time with your updated Availability.
Although these files are constantly updated by WebBookingPro, the calendar channel itself only "asks" for new information in the file approximately every 6 hours.
For Airbnb specifically, they "pull" data from WebBookignPro every hour. This is their native update timeframe.
Some channels use calendar check in real-time.
All Calendar Channels are considered One-Way channels. If you choose to use iCAL Connection, you will have to manually adjust inventory for any incoming bookings coming from those channels.
Example: Let's say you choose to connect HomeAway (Vrbo) to WebookingPro. Here is the chain of events:
Cancellations from a calendar channel cannot be transmitted to any 3rd parties (including WebBookingPro).
Since WebBookingPro is unaware of any Calendar Channel cancellations, the property must manage the inventory manually.
Example:
Every OTA has in his extranet part where you enter direct link (URL) to iCAL for each room type.
Those links are created by WebBookingPro.
Log in WebBookingPro, go to Hotel Management - Hotel Info and find [Settings] under Channel Manager.
if you do not see iCAL under listed Channel Managers, choose "Add New", select iCAL and click "Create".
Now click on [Map Rooms] under iCAL row and you will find all links for your property.
For each property room type or room or house/Villa you will find those links:
Copy those links and past them in your desired OTA's extranet.
To update inventory for specific room(s) and specific period, please use following XML request:
<?xml version="1.0" encoding="UTF-8"?><request apiKey="your_api_key" userName="your_property_username" password="your_property_password"> <updateInventory hotelId="111" roomId="300" dateFrom="2021-04-29" dateTo="2021-04-30" nrRooms="2"> <updateInventory hotelId="111" roomId="300" dateFrom="2021-05-01" dateTo="2021-05-31" nrRooms="3" LOS="3"> <updateInventory hotelId="111" roomId="300" dateFrom="2021-06-01" dateTo="2022-05-31" Closed="1"> <updateInventory hotelId="111" roomId="301" dateFrom="2021-06-01" dateTo="2022-05-31" Closed="1"> </request>
<request> can have multiple <updateInventory> objects.
hotelId, roomdId, dateFrom, dateTo are mandatory attributes of <updateInventory> object.
nrRooms sends number of available rooms. If not set nrRooms is set to 0!
LOS sends MinLOS if applicable. If not set MinLOS value is not changed!
Closed=1 closes room for specific period, Closed=0 opens room for specific period. If not set Closed value is not changed!
CFA=1 closes room for arrival for specific period, CFA=0 resets. If not set CFA value is not changed!
CFD=1 closes room for departure for specific period, CFD=0 resets. If not set CFD value is not changed!
To get details about specific booking use the following XML request:
<?xml version="1.0" encoding="UTF-8"?><request apiKey="your_api_key" userName="your_property_username" password="your_property_password"> <getBookingDetails hotelId="111" bookingid="3007995073"/> </request>
Both hotelId and bookingid are required.
If request was successful you should retrieve XML like this:
<?xml version="1.0" encoding="UTF-8"?> <Response><booking><bookingid>3007995073</bookingid><bookingdate>2021-04-27T13:12:03+02:00</bookingdate><modifieddate>2021-04-29T09:44:04+02:00</modifieddate><status>2</status><payment_info/><source>boo</source><additional_info>This is a Risk-Free Reservation. Upgraded policy: Free cancellation until 2 days before check-in. Please note that the credit card details have been updated. We recommend validating the card as soon as possible. For charging the card, you can follow your usual process. More information can be found at https://admin.booking.com/hotel/hoteladmin/extranet_ng/manage/booking.html?</additional_info><currency>EUR</currency><total>169.02</total><extras_fee>0.00</extras_fee><guest_tax>2.70</guest_tax><first_name>Mirko</first_name><last_name>Miocic</last_name><birth_date>0000-00-00</birth_date><address/><city/><country>HR</country><phone>+385 90 1111111</phone><email>mmmmmmmm@guest.booking.com</email><Rooms><Room id="300" count="1" checkin="2021-05-01" checkout="2021-05-02" adults="2" children="0" price="166.32" extra_beds="0" extra_beds_charge="0.00" mealplan=""/></Rooms></booking></Response>
bookingdate is always retrieved in RFC3339 DateTime format.
modifieddate is retrieved in RFC3339 only when reservation was modified.
status_changed is retrieved in RFC3339 only when reservation's status was changed (e.g. to Cancelled).
payment_info - shows payment text sent via some OTAs
total - total value of reservation
currency - currency code
guest_tax - if available taxes included in reservation like touristic tax
extras_fee - if avilable, extras included in reservation like parking, crib, ...
additional_info - all text sent via OTAs or additional notes sent via direct WBP reservation
source - code of source
first_name, last_name, birth_date, phone, email, city, country - all information about guest that made reservation.
<Rooms> object contains 1 or several <room> elements.
each <room> element has following attributes
id - id of room
count - number of reserved rooms
checkin - checkin date in format YYYY-MM-DD
checkout - checkout date in format YYYY-MM-DD
adults - number of adults
children - number of children
price - price of specific room
extra_beds - number of extra beds
extra_beds_charge
meal_plan - text about meal plan
meal_plan_price - additional price for choosed meal_plan if set
To get bookings for hotelId and specific period use the following XML request:
<?xml version="1.0" encoding="UTF-8"?><request apiKey="your_api_key" userName="your_property_username" password="your_property_password"> <getBookings hotelId="111" dateFrom="2021-04-28" dateTo="2021-04-29"/> </Request>
hotelId, dateFrom and dateTo attributes are all required.
dateFrom and dateTo should be in one of following formats:
If request was successful you should retrieve XML like this:
<?xml version="1.0" encoding="UTF-8"?> <Response><booking bookingid="3986846085" bookingdate="2021-04-27T19:56:02+02:00" modifieddate="2021-04-29T08:58:03+02:00" status_changed="2021-04-29T08:58:03+02:00" status="6" source="boo"/><booking bookingid="1W38549DKA" bookingdate="2021-04-28T11:19:22+02:00" status_changed="2021-04-28T11:21:04+02:00" status="2" source=""/><booking bookingid="5W04MQYN2O" bookingdate="2021-04-28T17:41:03+02:00" status_changed="2021-04-28T17:43:52+02:00" status="2" source=""/><booking bookingid="GWPJ50QCYM" bookingdate="2021-04-28T18:38:15+02:00" status_changed="2021-04-28T18:38:50+02:00" status="2" source=""/><booking bookingid="3390878623" bookingdate="2021-04-24T17:08:02+02:00" modifieddate="2021-04-28T20:04:04+02:00" status="2" source="boo"/><booking bookingid="2762087198" bookingdate="2021-04-29T08:32:02+02:00" status="2" source="boo"/><booking bookingid="3007995072" bookingdate="2021-04-27T13:12:03+02:00" modifieddate="2021-04-29T09:44:04+02:00" status="2" source="boo"/></Response>
bookingdate, modifiedddate, status_changed are DateTime in RFC3339 format with timezone correction.
modifieddate shows only if reservation is modified or status changed.
status_changed shows only if status has been modified with time of modify.
source represents OTA shortcode or if empty it means direct WBP reservation
status can be:
To get rooms associated with specific hotelId use the following XML request:
<?xml version="1.0" encoding="UTF-8"?><request apiKey="your_api_key" userName="your_property_username" password="your_property_password"> <getRooms hotelId="111"/> </request>
If request was successful you should retrieve XML like this:
<?xml version="1.0" encoding="UTF-8"?> <Response><room id="300" description="Double Room with Sea View"/><room id="301" description="Suite"/></Response>
To get hotels connected with one user send following XML request to API base url.
<?xml version="1.0" encoding="UTF-8"?><request apiKey="your_api_key" userName="your_property_username" password="your_property_password"> <getHotels/> </request>
If request was successfull you should retrive XML like this
<?xml version="1.0" encoding="UTF-8"?> <Response><hotel id="111" description="Bellevue Hotel"/><hotel id="112" description="Bellevue Residence"/></Response>
This document is the official reference for the WebBookingPro Connectivity API. The WBP Connectivity APIs enable Connectivity Partners to send and retrieve data for properties on WBP. All data sent to WBP is updated on all connected partners (e.g. OTAs, other Channel Managers, Meta Search Portals, ...) simultaneously.
If you are developing PMS your customers can control over all inventory availability and restrictions and view reservations with all needed information in your interface. This creates added value for your solution to integrate with direct reservations on property website or with connected OTAs without managing several Extranets (Administration areas).
The methods that retrieve or submit data require a POST request method.
We use simple XML structure for input and output, encoded in UTF-8.
All requests to the API must use the HTTPS protocol (Hypertext Transfer Protocol [HTTP/1.1], over Transport Layer Security [TLS 1.2].
All requests must include three important elements:
The WBP Connectivity API (version 2.0) use following url:
https://secure.webbookingpro.com/api/xml2.php