Functional Errors (HTTP 200)
These errors may occur when the request can not be satisfied within the CRS due to business reasons. Reasons may include the property being temporarily inactive or there is no available inventory for the requested date of arrival. These HTTP 200 errors only return from calls made to Dcshop. They will not be seen calling DCRes. An example:
{
"arrivalDate": "2019-12-22",
"departureDate": "2019-12-26",
"lengthOfStay": 735,
"numAdults": 2,
"propCode": "LONSB",
"statusCode": 1740,
"statusMessage": "REQUESTED RATE PLANS ARE NOT AVAILABLE"
}
DCShop responses that return availablity will always return statusCode=0.
Examples of HTTP200 responses that did not return availability from DCShop can return the following status codes:
HTTP 200 Codes - CRS errors
Status | Message | Comments |
---|---|---|
1 | Reservation System error | Error due to a temporary CRS system performance issue. Client is advised to retry the booking. |
7 | Invalid length of stay was specified | |
14 | Invalid property code was specified | |
51 | PRESELL 01 JAN 2020 | Various temporarily inactive property errors due to reasons such as brand change / under construction, etc. NOTE: This is an example message, the actual message will be specific to the property |
52 | Property Inactive | |
610 | The data base table has too many records to support this transaction | Dates searched that the CRS could not provide availability for. Most frequently occurs if searched dates are in past or father than 1 year in the future |
1740 | Requested Rate Plans Are Not Available |
Bad Request (HTTP 400)
Swagger Error Response and Notification Definition
HTTP 400 responses can be returned due to malformed JSON requests or data that fails validation within API or CRS.
By default, the response will contain an ‘ErrorDetail’ block defining the error class and the service context that triggered the response. The ErrorDetail may include one or more ‘Notifications’ which provide additional details of the specific error type and fields affected (optional). HTTP400 error responses will include error information including the Hilton custom error code as well as associated OTA error code based on OTA 2014B ERR table. The full list of errors that are currently supported can be found in this spreadsheet. OTA Error Codes.xlsm
Swagger ErrorDetail
ErrorDetail:
required:
- context
- code
- message
type: object
properties:
context:
type: string
code:
type: integer
message:
type: string
notifications:
type: array
items:
$ref: '#/definitions/ErrorNotification'
Swagger ErrorNotification
ErrorNotification:
required:
- message
type: object
properties:
code:
type: string
otaErrorCode:
type: integer
description: Online travel agency error code.
fields:
type: array
items:
type: string
message:
type: string
Error Response Example with Notification
For HTTP status code 400, an error body will be returned with the details about the errors. The body of the response will be in the following format:
Expanded details on cause of common errors that clients have reported trouble resolving.
HTTP 400 Codes - API errors
Status | Message | Sub Code | Sub Message | Comments |
---|---|---|---|---|
999 | Constraint Violation | 16 | Value is required | Check the data in the error message field to see if it follows Hilton's API specifications: DC Shop | Hilton Dev Portal |
1001 | Constraint Violation | 22 | String must match the specified regular expression. | Check the data in the error message field to see if it follows Hilton's API specifications: DC Reservation | Hilton Dev Portal |
999 | Constraint Violation | 22 | String must match the specified regular expression. | Check the data in the error message field to see if it follows Hilton's API specifications: DC Shop | Hilton Dev Portal |
999 | Constraint Violation | 24 | The number of elements in the collection must be between the boundaries. | Check the data in the error message field to see if it follows Hilton's API specifications: DC Shop | Hilton Dev Portal |
998 | Invalid XXX | 31 | Invalid JSON Parameter Value | Check the data in the error message field to see if it follows Hilton's API specifications: DC Reservation | Hilton Dev Portal |
1001 | Reservation Error | 45 | No travel agent address | Modify request did not pass TA address thus treated as attempt to remove from reservation. |
1001 | Reservation Error | 46 | No address | Check address against Hilton API specifications: DC Reservation | Hilton Dev Portal |
1001 | Reservation Error | 75 | Maximum occupancy restriction exceeded | Selected Room Type does not accommodate the number of guests in requests; please choose a different room type. For more information refer to question S7 on : Commonly Asked Questions | Hilton Dev Portal |
1001 | Reservation Error | 81 | Invalid credit/debit card vendor | Invalid Credit Card number provide in the Book Request. |
1001 | Reservation Error | 83 | Invalid expiration date | Invalid Credit Card number provide in the Book Request. |
1001 | Reservation Error | 84 | Invalid credit/debit card number | Invalid Credit Card number provide in the Book Request. |
1001 | Reservation Error | 123 | Client File of this type previously accepted OR GNR/Client File conflict, same type but different IDs | These errors indicate multiple clientIds of the same type are being passed in the clientAccounts field; please review the request and ensure only one clientId of each type is being passed. Please check Hilton API specifications: DC Reservation | Hilton Dev Portal |
1001 | Reservation Error | 180 | Operator ID 'xxx' is invalid at location 'TVPT' | Hilton configuration error |
1001 | Reservation Error | 234 | Record not found | The ID number provided is not valid or was not found in the system. This applies to any ID number, including Client ID (both Corporate & Travel Agent), Member ID (e.g., Hilton Honors Number, Travel Partner Number), etc. |
1001 | Reservation Error | 283 | Duplicate guest names | The Guest Name and one of the additionalNames are identical. |
1001 | Reservation Error | 284 | There cannot be more names than max occ | The number of guest names passed on the request exceed the number of people allowed in the room type NOTE: This includes additional names. |
1001 | Reservation Error | 291 | Minimum length of stay not met on requested date | Please try changing the room type or length of stay to meet the requirement. |
1001 | Reservation Error | 322 | Insufficient inventory for transaction | The inventory for the selected roomTypeCode and ratePlanCode is not available. Try a different roomTypeCode and/or ratePlanCode. |
1001 | Reservation Error | 367 | guarantee.paymentCard.cardNumber. String must match the specified regular expression | Invalid Credit Card number provide in the Book Request. |
1001 | Reservation Error | 387 | Insufficient guarantee | The guarMedthodcode provided in the booking request does not meet the guarantee requirements of the RatePlan. Please use a code from the guaranteeMethods listed in the shop response. |
1001 | Reservation Error | 397 | There cannot be more names than max occ | The number of guest names passed on the request exceed the number of people allowed in the room type. (NOTE: This includes additional names.) See Common Questions | Hilton Dev Portal for documentation for additional information on determining maximum occupancy |
1001 | Reservation Error | 448 | Guest client file required | Some required fields in the clientAccounts section of the Book request have not been provided. |
1001 | Reservation Error | 450 | Invalid Name Segment | The firstName and/or lastName do not adhere to the naming constraints as outlined in the API specifications on the StandardName-DcRes | DC Reservation | Hilton Dev Portal for documentation. |
997 | Bad Request | 502 | Value not valid in this context. | Check the data in the error message field to see if it follows Hilton's API specifications: DC Shop | Hilton Dev Portal |
997 | Bad Request | 503 | The arrival date must be less than or equal to departure date. | Check request to ensure arrival date is not chronologically later than the departure date. |
997 | Bad Request | 508 | One of the following is required. | Check the request and ensure value mentioned in the field is being supplied, per API REST specifications: DC Shop | Hilton Dev Portal Examples of fields: [ "numAdults","numChildren"] |
997 | Bad Request | 511 | Must have at least one occupant. | Verify the numAdults data sent in the request. |
1001 | Reservation Error | 612 | Need a valid credit/debit card or special customer number | The payment details provided in the booking are invalid. |
400 | Reservation Error | 1182 | Guarantee type (Guaranteed) is not valid for this property | The credit card type used is not accepted for guarantees. |