API Change Log

2019/11/07

Price API--Single Hotel/Multiple Hotels

• New field bookingRule@userProperty, to limit particular price to consumers of specific menbership level.
• New field bookingRule@ip, to limit particular price to consumers of specific ip address.
• New field bookingTime@maxAdvanceDays/bookingTime@minAdvanceDays/bookingTime@minAdvanceHours, to set visible time of particular price.

2018/08/31

1.Hotel List

• The original version hotel@name can be passed in Chinese or English, modified to please use the English name.
• New field hotel@nameCN, as hotel name (Chinese).
• New field hotel@coordinateProvider as Coordinate Provider.
• New field hotel@longitude.
• New field hotel@latitude.

2.New field hotel@latitude

• The original version hotel@name can be passed in Chinese or English, modified to please use the English name.
• New field hotel@nameCN, as hotel name (Chinese).
• New field hotel@coordinateProvider as Coordinate Provider.
• New field hotel@longitude.
• New field hotel@latitude.
• The original version room@name can be passed in Chinese or English, modified to please use the English name.
• New field room@nameCN, as room name (Chinese).
• New field window.

2016/10/28

1. price change

price change API aims to reduce the server load of supplier, suppose you have 10,000 hotels. the room rate caches for 1 hour, after cache expires, qunar will access your price API to obtain the price of the 10,000 hotels whether there is modification or not. If the supplier supports price change API, and there are 5 hotels with price modifications after 1 hour, qunar will access the price API for the 5 hotels only. Prices for other hotels are considered effective.

2016/05/20

1. Price API--Multiple Hotels

   • To reduce the flow of pages from the price change frequency;
   • while effectively reducing the number of visits to the agent.

   Now , We additionally provide an interface that use the city code or number of hotelId as a request parameter.

2016/05/16

1. For cancelRequest

   if requiredAction exists, this means that the request is sent from Qunar's backend on the user'S request.

   API original description：

   The price provider should return a with result = PROCESSING, and AGREE_UNSUBSCRIBE or REFUSE_UNSUBSCRIBE through Order operation API later on.

   Production Environment：

   The order status of the system-qta has been changed to "canceled", this status is the final state status. So the agents no longer need to operate.

   Delete the contents are as follows；

   1) opt : AGREE_UNSUBSCRIBE / REFUSE_UNSUBSCRIBE

   2) cancelResponse : result= PROCESSING.

2016/04/08

1. qunarOrderQueryResponse--channel,deposit：

   These two nodes (channel,deposit) has no effect, it is hereby deleted(It does not affect the business logic).

<qunarOrderQueryResponse>
    <orderInfo>
        <orderNum>j3gm141219163017759</qunarOrderNum><!-- unique order id at Qunar  -->
        <orderId>9987654</orderId><!-- unique order id at wrapper -->
        <payType>PREPAY</payType>
        <qunarStatus>50</qunarStatus>
        <channel>MAIN</channel>
        <deposit></deposit>
        <roomNum>2</roomNum>


</qunarOrderQueryResponse>

change to :

<qunarOrderQueryResponse>
    <orderInfo>
        <orderNum>j3gm141219163017759</orderNum><!-- unique order id at Qunar  -->
        <orderId>9987654</orderId><!-- unique order id at wrapper -->
        <payType>PREPAY</payType>
        <qunarStatus>50</qunarStatus>
        <roomNum>2</roomNum>

2016/03/02

1. priceResponse--occupancyNumber：

   If the prices of your hotel will be changed with the difference numbers of guests.

   Please add occupancyNumber behind maxOccupany in <priceResponse>.

   For example, if the response is for 1 adult to check in but the max occupancy is 2 adults, please response like this : maxOccupancy="2" occupancyNumber="1"

 <room id="9986" name="特色房" broadband="FREE" payType="PREPAY" prices="200|200" status="ACTIVE|ACTIVE" counts="5|5" 
        roomRate="180|180" taxAndFee="20|20" maxOccupancy="2" occupancyNumber="2"
        freeChildrenNumber="1" freeChildrenAgeLimit="8" instantConfirmRoomCount="3|3" wifi="FREE" 
        checkinTime="" checkoutTime="" area="" >
        ...

2016/2/29

• bedType preference for 2 single beds /1 double beds：

  Xml as following will not be recognized and provide bed type preference to users：

    <bedType relation="OR">
        <beds code="OTHERS" count="1" desc="1 Double Bed or 2 Single Beds" seq="1" size=""/>
    </bedType>

Right xml should be like following example:

    <bedType relation="OR">
        <beds code="Double" count="1" desc="1 Double Bed " seq="1" size=""/>
        <beds code="Single" count="2" desc="2 Single Beds" seq="2" size=""/>
    </bedType>

• bedType preference for "OTHER"：

  Example:

    <bedType relation="">
        <beds code="OTHERS" count="1" desc="1 Double Bed and 1 Sofa Bed " seq="1" size=""/>
    </bedType>

When you use `beds code="OTHERS"`, `bedType description` should be listed with

If bed type is unknown, "OTHERS" can be used as desc don’t use blank or other sayings.

If the room contains multiple bed types, please list all the beds in one string like desc="1 Double Bed and 1 Sofa Bed ".