4.2. Managing Property Status
POST /cm/property/status
Description
This section outlines the ability to deactivate or delete a property
Body parameter
HotelSummary in OTA2017B format which specifies the property and status
Name : body
Flags : required
Type : OTA_HotelSummaryNotifRQ
Responses
| HTTP Code | Description | Schema |
|---|---|---|
200 |
The request has been accepted for processing |
|
400 |
The request content was malformed |
|
401 |
The supplier was unauthorized |
Consumes
-
application/xml
Produces
-
application/xml
Tags
-
PropertyStatus
Security
| Type | Name |
|---|---|
apiKey |
Example HTTP request
Request path
/cm/property/status
Request body
<?xml version="1.0" encoding="UTF-8"?>
<OTA_HotelSummaryNotifRQ xmlns="http://www.opentravel.org/OTA/2003/05" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" HotelCode="9612080" xsi:schemaLocation="http://www.opentravel.org/2017B/OTA_HotelSummaryNotifRQ.xsd">
<HotelSummaryMessages>
<HotelSummaryMessage StatusType="Closed"/>
</HotelSummaryMessages>
</OTA_HotelSummaryNotifRQ>Example HTTP response
Response 200
<?xml version="1.0" encoding="UTF-8"?>
<OTA_HotelSummaryNotifRS CorrelationID="8b417d6a-f3df-4d65-870c-240378b8ad3e">
<Success/>
</OTA_HotelSummaryNotifRS>Response 400
<?xml version="1.0" encoding="UTF-8"?>
<OTA_HotelSummaryNotifRS CorrelationID="8b417d6a-f3df-4d65-870c-240378b8ad3e">
<Errors>
<Error Code="321" ShortText="Required field missing" Status="NotProcessed"/>
</Errors>
</OTA_HotelSummaryNotifRS>Response 401
<?xml version="1.0" encoding="UTF-8"?>
<OTA_HotelSummaryNotifRS CorrelationID="8b417d6a-f3df-4d65-870c-240378b8ad3e">
<Errors>
<Error Code="497" ShortText="Authorization error" Status="NotProcessed"/>
</Errors>
</OTA_HotelSummaryNotifRS>Please note that the Content Push API only supports updating the property status to “Closed.” A property cannot be reactivated through the API. If the property needs to be reactivated, please contact [email protected] for further assistance.