To override the Content-type in your clients, use the HTTP Accept Header, append the .xml suffix or ?format=xml
HTTP + XML
The following are sample HTTP requests and responses.
The placeholders shown need to be replaced with actual values.
POST /hotelinventoryrestriction/{SubscriptionId}/{CendynPropertyId} HTTP/1.1
Host: cert.cendyn.com
Accept: application/xml
Content-Type: application/xml
Content-Length: length
<HotelInventoryRestriction xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/CenResSS.ServiceModel">
<CendynPropertyId>String</CendynPropertyId>
<InventoryRestriction>
<Available>false</Available>
<ClosedToArrival>false</ClosedToArrival>
<ClosedToDeparture>false</ClosedToDeparture>
<EndDate>0001-01-01T00:00:00</EndDate>
<HotelCode>String</HotelCode>
<IncludeFriday>false</IncludeFriday>
<IncludeMonday>false</IncludeMonday>
<IncludeSaturday>false</IncludeSaturday>
<IncludeSunday>false</IncludeSunday>
<IncludeThursday>false</IncludeThursday>
<IncludeTuesday>false</IncludeTuesday>
<IncludeWednesday>false</IncludeWednesday>
<MaxLOS>0</MaxLOS>
<MaxLOSThruStay>0</MaxLOSThruStay>
<MinLOS>0</MinLOS>
<MinLOSThruStay>0</MinLOSThruStay>
<RateCode>String</RateCode>
<RestrictRateBy>String</RestrictRateBy>
<RestrictRoomBy>String</RestrictRoomBy>
<RestrictionCode>String</RestrictionCode>
<RestrictionType>String</RestrictionType>
<RoomClass>String</RoomClass>
<RoomCode>String</RoomCode>
<SourceID>String</SourceID>
<SourceName>String</SourceName>
<StartDate>0001-01-01T00:00:00</StartDate>
</InventoryRestriction>
<SubscriptionId>String</SubscriptionId>
</HotelInventoryRestriction>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
<Response xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/CenResSS.ServiceModel">
<ErrorCount>0</ErrorCount>
<RecordCount>0</RecordCount>
<StatusCode>String</StatusCode>
</Response>