Error handlingCopy link

Error messaging in Product API helps you understand why a read, create, or update request is denied.

Connectivity errors

Connectivity errors are reported when communication disruption occurs between Expedia Group and your software.

If the problem is:

• Connection timeout (before establishing connection)
• Cannot resolve host name
• Cannot establish connection

Before looking for assistance, you should:

1. Verify the URL used to connect to the API and make sure the address starts with https://
2. Verify the domain name, and make sure that the address you are using is the right one for the environment you are targeting. Do not try to send QA information to production, or vice-versa.
3. If your system is behind a firewall, make sure that port 443 is opened for connection to Expedia's production environment.
4. Retry. If additional assistance is required, contact us.

Read (GET) response errors

There are two different read operations available against Product API’s resources:

• To get a specific resource, the resource ID needs to be specified on the URL. Example: /products/properties/{propertyId}

• To get all the active resources in the system, omit the resource ID on the URL. Example: /products/properties/

If a response doesn’t contain an Entity, it will contain Errors:

1{
2  "errors": [
3    {
4      "code": 1000,
5      "message": "Access denied: your account is not authorized to manage this property."
6    }
7  ]
8}

Entity vs errors

Entity and errors are in the same wrapper because most frameworks will de-serialize responses automatically, but require a target type to which the response will be deserialized.

Both successful and unsuccessful responses are returned by the same DTO, but can have either entity or errors, never both.

A Java implementation to handle this, using Spring’s RestTemplate, could look like this:

1ResponseEntity<ResponseWrapperDTO<RoomTypeDTO>> response = restTemplate.exchange(
2  "url",
3  HttpMethod.POST,
4  entity,
5  new ParameterizedTypeReference<ResponseWrapperDTO<RoomTypeDTO>>() {}
6);

Error codes and descriptions

Success responses:

The API will leverage HTTP status codes as defined by RFC 2616, Section 10. Users should expect HTTP status codes from the API as indicated in the table below.

HTTP status codes