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

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