Error and Warning
In this chapter we will list the errors and warnings of HotelX booking flow.
In the table below, we have structured a relation of all the Errors that can be returned in HotelX booking flow
|ACCESS_ERROR||VALIDATION_ERROR||No valid accesses found||The access is not found or it has no permission, or you are using a test access and you need to add the testMode.|
|MISSING_FIELD||VALIDATION_ERROR||According to the case||Some mandatory fields are missing in input|
|INTERNAL_ERROR||API_ERROR||According to the case||Covers any unexpected error or errors due to internal service|
|ALL_PROCESSES_FAILED||PROCESS_ERROR||See warnings for more information||This occurs when no options are returned for all accesses after applying a plugin (blacklist, filter, mapping code), commission, etc., it may also be caused by a wrong default setting, In the warning node you will find detailed information about the cause.|
|TIMEOUT||CONNECTION_ERROR||According to the case||This occurs due to a connection timeout|
|REFERENCE_NOT_EXISTS||BOOKING_ERROR||According to the case||This occurs when the booking reference provided is not available in the supplier system|
In this section we will expand on all the Warnings that can be returned in HotelX booking flow. There are two types of warnings, HotelX warnings and Connection warnings.
In the table below, we have structured a relation of all the Warnings that can be returned in HotelX.
|WRONG_FIELD||VALIDATION_ERROR||According to the case||A field or fields in the request are not correct|
|INTERNAL_ERROR||MAPPING_ERROR||According to the case||Error produced when mapping codes, it usually happens regarding hotel mapping|
|COMMISSION_NOT_FOUND||API_ERROR||According to the case||This occurs when the options are discarded because the supplier returns options with a negative commission that does not allow the calculation of the net price. You need to upload the commission file to solve it|
|WRONG_FIELD||PLUGIN_ERROR||According to the case||It occurs when the input of the plugin is misintroduced or misconstructed|
|BLACKLIST||PLUGIN_ERROR||According to the case||It occurs when the hotels or accesses are blacklisted|
This type of warnings contains the supplier original error codes. This type of error codes are classified as warning codes because whenever more than 1 supplier is requested, some of those suppliers may return an error while others may return the response, accordingly. In those cases, if at least one of the suppliers returns results an error cannot be returned, hence those results will be displayed in the response, and for those accesses which have not returned results a warning will be returned.
|According to supplier error code||101||According to the case||System Exception (Exception not controlled or not classified as general exception).|
|According to supplier error code||102||According to the case||It contains supplier original error and code, for more detail you need to see description or contact the supplier|
|According to supplier error code||104||According to the case||Timeout, timeout due to supplier, not HotelX system|
|According to supplier error code||105||According to the case||Communication Error with a specific supplier|
|According to supplier error code||204||No results found||Supplier doesn’t return any options|
|According to supplier error code||205||According to the case||The Supplier doesn’t accept the occupancies configuration.|
|According to supplier error code||206||According to the case||The Supplier doesn’t accept the dates RQ.|
|According to supplier error code||207||According to the case||The Supplier doesn’t accept the request RQ.|
|According to supplier error code||301||According to the case||Option not found in Quote.|