...
EchoTokens are essential for all requests being made over the pmsXchange v2 as per the following link - EchoToken, Timestamp and POS.NOTE:
| Info |
|---|
Please ensure that you implement EchoTokens that are as 'unique' as possible to ensure that log trawling for troubleshooting purposes on either side is quick and efficient. Implementing GUIDs are recommended and more information about GUID can be found - http://en.wikipedia.org/wiki/Globally_unique_identifier. |
Linespacing
All Soap XML requests made to pmsXchange should be contained on one line with no linespacing. We ask this to assist our support teams in extracting messages from our logs.
Content-Type
The ‘Content-Type’ for all Soap XML requests made to pmsXchange V2 must be 'text/xml; charset=utf-8'. Any other ‘Content-Type’ will not be accepted.
...
It is expected that your PMS has a robust error handling process whereby errors can be queued and resent. It's also expected that you make hoteliers aware of errors affecting the syncing of their data over pmsXchange. More information can be found below under 'Availability (Restrictions &/OR Inventory) Uploads' and 'Rate Uploads' and within our Error Handling page.
Reservation delivery
...