We define the other users you may notice here:

Admin - this meant the booking was created by a travel system that is part of the Global Booking Network (GDS, Pegasus, OTA system_ that you use BookingCenter to connect to.

Requests - this meant the booking was created by the Booking Engine that BookingCenter provides for making bookings, usually from your website, FaceBook, or TripAdvisor listing.

XML - this meant the booking was created by an XML interface developed by your webmaster; or an XML service you use such as Easy Innkeeper, buuteeq, or others we support.

• Availability and booking interface between BookingCenter's system and a customer's website application presented as a web service using SOAP.
• SOAP messages using the OTA schemas based on the OTA 2008B Specification from http://www.opentravel.org/  with online documentation is available at http://opentravelmodel.net/pubs/specifications/Specifications.html.

Platform support

• Our SOAP WSDLs are compatible with Microsoft's .NET platform and NuSOAP (the PHP variant for SOAP). Options exist for other development platforms, but we support these.
• No restrictions on server implementation, as it has no impact on client.
• SSL security certificate needs to be mainatined by the XML developer, as the 'host' website where shopping and transactions occur is the website serving the web pages and not BookingCenter's secure server. The communication between the XML developer and BookingCenter, however, does take place over secure SSL communication.

Service Definition

• The XML Service supports multiple search criteria such as availability, rates, rooms, packages, amenities, activities, etc.
• Availability is data is taken from data coming from any Desktop Pro, MyPMS, or Management Tool customers.

References

• http://www.opentravel.org/
• http://ws.apache.org/axis/
• http://ws.apache.org/wss4j/
• Our KnowledgeBase area for XML developers: https://support.bookingcenter.com/index.php?/Knowledgebase/List/Index/8/xml-team

Support

We have a series of knowledgeBase articles at: https://support.bookingcenter.com/index.php?/Knowledgebase/List/Index/8/xml-team that can help you get going and 'scope' out the development of an XML web services project using BookingCenter.  BookingCenter will only provide general support for a webmaster/developer who attempts the XML web service for a customer. But BookingCenter can be hired to develop a custom 'Booking Engine' or other application. Just contact us at: http://www.bookingcenter.com/contact to request a quote after you send us a 'wire frame' and/or diagram of your intended screens and detailed functionality.  We need a detailed description of what you want prior to quoting a price or time estimate.

In order to examine the BookingCenter API documents, you will need to download the NDA (non disclosure, available at: http://files.bookingcenter.com/API_use_NDA.pdf, sign it and email it to info@bookingcenter.com or fax it to us at +1-718-228-5959 (please append a note telling us which BookingCenter customer you are working with). We will then send the appropriate documentation, login and info for you to test your code against our 'Test System' (if your customer is there), and then release to our production systems once readied. 

Also, you can 'View Tickets' you've already created, and open or review those tickets that are 'closed'.  You can always find articles in the KnowledgeBase that will help improve use of the BookingCenter tools and services. This area is managed 24 x 7.  

There are times when a property wishes to have multiple Users attached to their 'company' so that multiple users gain access to the 'tickets' raised.  To do this, have your new user visit: https://support.bookingcenter.com/ and click 'subscribe' to subscribe to the Support Area.  If they use the domain name of your property (such as me@myhotel.com where 'myhotel.com' is your host/domain name) when subscribing, our system will automatically attach them to your property, so they are added as a User who can login and view tickets for your property.  If they 'subscribe' with a different email address, such as me@gmail.com' then the system will not know they are suppord to be associated to your property, and you must enter a ticket and ask us to attach that specific user to your property account. Just send us the email they used to subscibe in a Ticket and we will then manually attach them to your propty profile in the Support Area.

There are a few key elements that are critical to understand with the OTAs and OOO:

1.        OOO is a "Room" Setting, but the OTA sells via Room Type, and
2.        When a room is set OOO, Booking.com and Expedia get availability updates, but not specific room updates

Below is an example of where it may appear that there was an overbooking, but this was not the case. Your property has three King rooms that have the following reservations for May 1^st and May 2^nd:

Room 106 - OOO has been set for May 7th and May 8th

Room 107 - Booking on May 7th; Open of May 8th

Room 108 - Open on May 7th; Booking of May 8th

As far as the OTAs are concerned for your King room type, it will show availability (1) on both March 7th and March 8^th (as you do have availability). If a two-day booking is made at the property, you will need to make some adjustments to the room if you want the guest in the same room for the duration of the stay.

Please note that this scenario does take place regardless of setting a room OOO, but is more common now with the current situation.

If you’re using the XML calls and you want to determine what setting to use you to save a booking with the Site’s Deposit and Cancelaltion policy text, policy, and amount, you should follow the steps below: 

#1 -  Make a call OTA_HotelDescriptiveContentInfo - Site Information: Policies 

Type: Policies
OTA_HotelDescriptiveContentInfoPort  
Test end point: https://ws-server-test.bookingcenter.com/hotel_information.php?wsdl

This will return the key attributes you need to make the OTA_HotelResPort (New Booking call) 

Sample PHP/SOAP code: