Table of Contents |
---|
Error Responses to SMX
Info |
---|
Important |
It is expected that your application has a robust error handling process in place. An error response should contain a short description of the error to assist our support teams.
Invalid Hotel Code
Code Block | ||
---|---|---|
| ||
<OTA_HotelResNotifRS xmlns="http://www.opentravel.org/OTA/2003/05" Version="1.0" TimeStamp="2005-08-01T09:30:47+08:00" EchoToken="abc123"> <Errors> <Error Type="6" Code="392">Invalid hotel code: ABC</Error> </Errors> </OTA_HotelResNotifRS> |
Required Information Not Present
Code Block | ||
---|---|---|
| ||
<OTA_HotelResNotifRS xmlns="http://www.opentravel.org/OTA/2003/05" Version="1.0" TimeStamp="2005-08-01T09:30:47+08:00" EchoToken="abc123"> <Errors> <Error Type="3" Code="321">Guest email address is required</Error> </Errors> </OTA_HotelResNotifRS> |
Recommended OTA Error Codes
SMX recommends (but is not limited to) the following error codes from OTA Warning Type (EWT). Any OTA Warning Type can be used.
Error Warning Type (EWT)
Code | OTA Description |
---|---|
1 | Unknown |
2 | No implementation |
3 | Biz rule |
4 | Authentication |
5 | Authentication timeout |
6 | Authorization |
7 | Protocol violation |
8 | Transaction model |
9 | Authentical model |
10 | Required field missing |
11 | Advisory |
12 | Processing exception |
13 | Application error |
Error Codes (ERR)
Error Codes - General
These are recommended (but not limited to) Error Codes to be returned for general errors. Any OTA Error Code (ERR) entry can be used.
...