CenResService

MessageAcknowledgement

The following routes are available for this service:
POST	/acknowlegement/{SubscriptionId}/{CendynPropertyId}

**MessageAcknowledgement** Parameters:
Name	Parameter	Data Type	Required
Acknowledgement	body	Acknowledgement	No
SubscriptionId	path	string	No
CendynPropertyId	path	string	No

**Acknowledgement** Parameters:
Name	Parameter	Data Type	Required
CendynPropertyID	form	string	No
HotelCode	form	string	No
Success	form	bool	No
EchoToken	form	string	No
UniqueIDs	form	List<UniqueIDType>	No
Messages	form	List<StatusMessage>	No

**UniqueIDType** Parameters:
Name	Parameter	Data Type	Required
ID	form	string	No
Type	form	string	No
Context	form	string	No

**StatusMessage** Parameters:
Name	Parameter	Data Type	Required
MessageType	form	StatusMessageType	No
Code	form	string	No
Message	form	string	No
Target	form	string	No

**StatusMessageType** Enum:
Info
Warning
Error

**Response** Parameters:
Name	Parameter	Data Type	Required
StatusCode	form	string	No
RecordCount	form	int	No
ErrorCount	form	int	No

To override the Content-type in your clients, use the HTTP Accept Header, append the .json suffix or ?format=json

To embed the response in a jsonp callback, append ?callback=myCallback

HTTP + JSON

The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.

POST /acknowlegement/{SubscriptionId}/{CendynPropertyId} HTTP/1.1 
Host: cert.cendyn.com 
Accept: application/json
Content-Type: application/json
Content-Length: length

{"acknowledgement":{"cendynPropertyID":"String","hotelCode":"String","success":false,"echoToken":"String","uniqueIDs":[{"id":"String","type":"String","context":"String"}],"messages":[{"messageType":"Info","code":"String","message":"String","target":"String"}]},"subscriptionId":"String","cendynPropertyId":"String"}

HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length

{"statusCode":"String","recordCount":0,"errorCount":0}