/
8. ERROR HANDLING

8. ERROR HANDLING

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:

8.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>

8.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

Element

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>

8.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>

8.4. ERROR AND WARNING CODES

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

8.4.1. TRANSFER AVAILABILITY

Warning/Error

Code

Short text

Possible reason

Status

Warning

15

Invalid date.

Supplier supports only dates in 'yyyy-MM-dd' format.

NOT_SENT

20

Number of passengers invalid.

  1. Supplier allows only 99 paxes max in request.

  2. Supplier allows only 9 paxes max in request.

NOT_SENT

26

At least one adult must be included.

At least one adult must be included.

NOT_SENT

161

Search criteria invalid.

  1. Supplier does not support transfers from city to city.

  2. Supplier does not support transfers to other cities.

NOT_SENT

172

Requested action not possible.

  1. Supplier supported only russian language.

  2. Supplier supported only currency RUB.

  3. There are transfers between two points in one city only.

  4. Transfer time has been changed to flight arrival time since the driver of the pickup car will check when the plane will land in order to be at the airport at the correct time.

  5. Supplier supports only search by city.

  6. Supplier does not have transfer for such destination.

NOT_SENT

172

Requested action not possible.

  1. Supplier doesn't support requested language. Language is different from what has been requested.

  2. The specified transfer time was not taken into account on search, since supplier doesn't support this.

SENT

184

Language code invalid.

Supplier does not support requested language.

NOT_SENT

253

Invalid pick up time.

Transfer details as well as price will be more precise if transfer time specified.

SENT

322

No availability.

 

NOT_SENT

357

Invalid city code specified.

Cannot find a city by IATA code.

NOT_SENT

400

Invalid property code

Invalid transfer code passes.

SENT

450

Unable to process.

 

SENT

558

Accounts are settled in a currency different from the quoted rate currency.

Rates or cancellation fee are returned in other currency than it was requested.

SENT

8.4.2. TRANSFER CHARGES

Warning/Error

Code

Short text

Possible reason

Status

Error

161

Search criteria invalid.

BookingCode 3e8 not found in HUB system.

NOT_SENT

Warning

189

The price has been changed.

The price has been changed.

SENT

Error

360

Error entry code.

There is no available information about cancellation fees for offer with bookingCode.

SENT

Warning

438

Requested rate not available.

  1. Offer availability status changed to AvailableForSale/OnRequest.

  2. Offer is not available anymore.

SENT

Warning

558

Accounts are settled in a currency different from the quoted rate currency.

Requested currency was CAD, but cancellation fees returned in USD.

SENT

8.4.3. RESERVATION INITIATE

8.4.4. RESERVATION CONFIRMATION

8.4.5. RESERVATION IGNORE

8.4.6. TRANSFER RETRIEVAL

8.4.7. CANCELLATION INITIATE

8.4.8. CANCELLATION CONFIRMATION

8.4.9. CANCELLATION IGNORE

8.4.10. TRANSFER DESCRIPTIVE INFO

Related content

2.3. TRANSFER AVAILABILITY RESPONSE
2.3. TRANSFER AVAILABILITY RESPONSE
Read with this
9. ERROR HANDLING
More like this
3.2. TRANSFER DESCRIPTIVE INFO RESPONSE
3.2. TRANSFER DESCRIPTIVE INFO RESPONSE
Read with this
5.5. RESERVATION CONFIRMATION REQUEST
5.5. RESERVATION CONFIRMATION REQUEST
Read with this