Each response from GP Travel HUB contains identifier whether it has been processed successfully or not - the elements <Success/>, <Warning/>, <Errors/>.

There are the following possible cases:

11.1. SUCCESS

Means that request was successfully sent and GP Travel HUB receives correct response from supplier without any warnings and errors from supplier.

<OTA_CancelRS Version="2" EchoToken="EchoToken" TransactionIdentifier="12232" xmlns:ota="http://www.opentravel.org/OTA/2003/05">
   <Success/>
</OTA_CancelRS>

11.2. WARNING

Means that request was successfully sent and GP Travel HUB receives correct response from supplier, but there are some warnings to pay attention.

There is a structure of Warning Response that is common for every response.

Warnings/Warning:

*mandatory

Element	Attribute	Type	Description	Min…Max occurs

Attribute	Type	Description	Min…Max occurs
Type*	integer (1, 3, 10, 11)	Defines type of the error or warning that occurred. Refers to OTA codes "Error Warning Type (EWT)”.	1…1
Code*	integer (1 - 1051)	Defines Error/Warning code.	1…1
Status*	string ("SENT", "NOT_SENT")	The values are (SENT \| NOT_SENT). Used for defining actual status of request.	1…1
ShortText*	string	Short error description.	1…1
RecordID	string	This attribute specifies supplier ID. If requests spans multiple suppliers, you can use this attribute to identify which supplier caused the problem.	0…1
Language*		For more information see Common Data Description section in Glossary.
DocURL	URI	If present, this URL refers to an online description of the error that occurred.	0…1
Tag	string	If present, this attribute may identify an unknown or misspelled tag that caused an error in processing.	0…1

<Warnings>
   <Warning Code="189" Language="en" RecordID="supplierCode" ShortText="Price has been changed." Status="SENT" Type="3"/>
</Warnings>

11.3. ERROR

Means that request was not sent to supplier (supplier temporally unavailable or failed data verification) or GP Travel HUB receives incorrect response or error from supplier. In case of error GP Travel HUB additionally returns original text from supplier.

Either there can be errors returned by GP Travel HUB itself. It mostly can be cases when a request validation not passed. Requests with incorrect format can not be processed by GP Travel HUB and passed to suppliers, so GP Travel HUB returns SOAP error message.

Errors/Error element has the same structure as Warnings/Warning.

<Errors>
   <Error Type="3" Code="172" ShortText="Generic error." Status="NOT_SENT" Tag="NORMAL" Language="en">Invalid client specified [ID:stb, IDContext: null, Instance:null]</Error>
</Errors>

11.4. ERROR AND WARNING CODES

Here we list all possible errors and warnings that can occur at rail messages.

11.4.1. RAIL SCHEDULE SEARCH

Warning/Error	Code	Short text	Possible reason	Status
Warning	450	Unable to process	Supplier Error	SENT

11.4.2. RAIL AVAILABILITY SEARCH

Warning/Error	Code	Short text	Possible reason	Status
Warning	22	Passengers exceed commercial rules	Passengers quantity in order can't be more than 4. Should be at least one adult. Count of children without seat should not be more than adults.	NOT_SENT
Warning	172	Requested action not possible	For Ukraine it is not allowed to book train tickets for children without seat	NOT_SENT
Warning	450	Unable to process	Supplier Error	SENT
Warning	430	Ok	Arrival and departure time is Moscow	SENT
Warning	172	Requested action not possible	Requested currency does not supported by supplier.	SENT
Warning	25	Passenger types not consistent	One Adult should be specified.	NOT_SENT

GP Travel HUB Rail User Guide

11. ERROR HANDLING

Analytics

11.1. SUCCESS

11.2. WARNING

11.3. ERROR

11.4. ERROR AND WARNING CODES

11.4.1. RAIL SCHEDULE SEARCH

11.4.2. RAIL AVAILABILITY SEARCH

11.4.3. RAIL PRICING

11.4.4. RAIL ROUTE

11.4.5. RAIL RESERVATION INITIATE

11.4.6. RAIL RESERVATION IGNORE

11.4.7. RAIL BOOKING RETRIEVAL

11.4.8. RAIL TICKETING

11.4.9. RAIL MODIFICATION INITIATE

11.4.10. RAIL MODIFICATION CONFIRMATION

11.4.11. RAIL CANCELLATION INITIATE

11.4.12. RAIL CANCELLATION CONFIRMATION