Invalid XML
Server must respond with an OTA_ErrorRS response :
<?xml version="1.0" encoding="UTF-8"?> <OTA_ErrorRS xmlns="http://www.opentravel.org/OTA/2003/05" ErrorCode="3006" Status="NotProcessed" ErrorMessage="Invalid XML" TimeStamp="2015-10-20T10:26:13+02:00" Version="1.0"/>
Other errors
In each message you can add an Errors node :
<?xml version="1.0" encoding="UTF-8"?>
<OTA_PingRQ>
<Errors>
<Error Code="101" Type="4" Status="NotProcessed" ShortText="Authentication refused">Authentication : login failed</Error>
</Errors>
</OTA_PingRQ>
Errors
Parent: OTA_HotelAvailNotifRS
Mandatory: No
Attributes: None
Child elements: Error
Error
Parent: Error
Mandatory: yes (If Errors is provided)
Attributes:
Name | Mandatory | Description |
|---|---|---|
| Type | Yes | OTA error code |
Code | Yes | OTA EWT code |
| Status | Yes | Default value "NotProcessed" (error) |
| ShortText | Yes | Textual explanation of the error. |
Child elements: None