ReferenceBooking Retrieval and Booking Confirmation API

Testing and troubleshooting

This section addresses the most common errors and technical difficulties that may be encountered when trying to connect to or develop for Booking Retrieval.

The API defines several different categories of errors. Expedia Group recommends a robust retry strategy when resolving errors.

Because Booking Retrieval API is only developed alongside the Booking Confirmation integration, this overview includes steps for both integrations and provides an outline of the entire testing process. Each step may take some time and require several iterations of your code.

Further details about self-testing will be provided by your Integration Specialist.

Connectivity errors

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

Possible scenarios include the following:

Connection cannot be established

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. The production URL for Booking Retrieval API is https://services.expediapartnercentral.com/eqc/br. The Booking Confirmation production endpoint URL is https://services.expediapartnercentral.com/eqc/bc.
  4. Retry. If additional assistance is required, contact us.
Connection refused

You receive this error when the API’s servers cannot accept any more connections than the ones currently established to other partners.

When this happens, you should simply enter in retry mode.

SSL certificate validation problems

To avoid issues with certificate signing authorities, anyone developing in Java should use version 1.4.2_13 or newer.

If you prefer to use an older version of Java or an in-house SSL library, you will need to import the Entrust CA certificate.

Connection established, system errors returned

These errors are automatically monitored by the Expedia Group API team, so there is no need to report them when they occur. The following are the most common errors and what you can do to resolve them.

Please note that every error returned by Expedia Group services contains a reference ID that can be used when communicating with us to investigate an issue.

Error Code

Error Description

Explanation and Partner Action

Retry?

4000, 4004, 4007

Internal system error, please try again in a few minutes.

Enter in incremental retry mode

Yes

4001

Internal timeout error, please try again in a few minutes

Enter in incremental retry mode

Yes

4100, 4101

Internal System Error. Do not retry this request. Our support team was notified of the problem.

Do not retry. Expedia Group has been notified of the issue and is working to find a solution. It is recommended to manually update in Partner Central.

No

4206

API interface is temporarily closed. Please try again in a few minutes.

Enter in incremental retry mode

Yes

5000

Internal database error. Please try again in a few minutes.

Enter in incremental retry mode

Yes

Connection established, no response

If your system establishes a connection to the API’s servers, but is not getting a response, you should:

Make sure your system is not closing the connection too early.

  • Some retrieval queries take longer than others. Expedia Group will keep connections active for up to 60 seconds. Therefore, your connections should stay open for at least 60 seconds as well.

    Make sure the content length specified in the HTTPS header corresponds to the actual length of the HTTPS request.

  • If the length specified in the header is longer than the message itself, the API waits for bytes that never arrive, and eventually times out.

Authentication errors

Errors related to authentication issues and what you should do if they occur. If you receive an authentication error, stop sending retrieval requests until the issue is resolved and contact your administrator to verify your system configuration and contact Expedia Group.

Error Code

Error Description

Explanation and Partner Action

Retry?

1000

Access denied: You are not authorized to use this API. Please contact Expedia to gain access.

Do not retry.For assistance, please contact us.

No

1001

Authentication error: invalid username or password

Do not retry.Verify username and password configured in your API interface. For assistance, please contact us.

No

1003

The user account provided doesn't have the right access level

Do not retry.For assistance, please contact us.

No

Parsing and protocol errors

Parsing or protocol errors occur when there are issues with the XML formatting. If these errors occur, you should stop sending retrieval requests until the issue is resolved and contact your administrator to identify the problem.

To avoid these errors, first parse the XML retrieval request to ensure it validates against the API’s schema.

Error Code

Error Description

Explanation and Partner Action

Retry?

2002

Parsing error: parsing_error_description

Correct XML format to comply with the API's specification. Developers of your system should be involved to find the problem.

Yes, after correction

2010

The namespace specified is invalid

Correct namespace and retry. Please note that namespaces are used to version Expedia Group service interfaces. Developers of your system should be involved to find the problem.

Yes, after correction

3010

Validation against schema failed because a value exceeds its defined length, the format is wrong, or because of another validation enforced by schema.

Correct the error in the system and drop this message (no retry). Developers of your system should be involved to find the problem.

No

3210

Communication error: exceed max number of connections allowed (1).

Partner tried to open more than one simultaneous connection per property. For any given property, never attempt to send 2 concurrent messages. Always wait for Expedia Group to respond before sending another message.

Yes, after closing the other connection

Response business errors

Once transactions have been submitted to the API system, you will receive an acknowledgement - either successful or negative.

Successful acknowledgements can contain warnings indicating part of the incoming request was not successfully processed and will include details about what failed. When warnings are returned, anything that is not specifically listed as a warning has been successfully processed.

Requests can contain multiple warnings. If too many warnings are generated, not all of them will be reported back to you in response. In this situation, the warning messages will clearly indicate that you should fix the problems with the request first before resubmitting to Expedia Group.

Error Code

Error Description

Explanation and Partner Action

Retry?

3015

Business validation error

You need to capture the description returned along with this code and should advise affected property of the error to verify if there is a problem with its system or the implementation of the API.

Yes, after verification

3202

Hotel ID not found. Either an invalid Hotel ID was specified or the account is not linked to this property.

Verify if there is a mapping issue in your system. If the mapping is correct, please verify that the user configured for the API has access to update this property (i.e. the user is able to access this property through Partner Central).

Yes, after verification

3206

Your account is not linked to any properties.

When calling Booking Retrieval service, ensure there is at least one property associated with the account.

Yes, after verification

3207

Hotel ID is a mandatory field for this request.

Specify the Hotel ID you need to retrieve bookings for.

Yes, after correction

3301

Update refused. No more than 10 confirmation numbers can be sent in a single message

Include fewer confirmation numbers in a single Booking Confirmation Request message. Resend the numbers by splitting them across multiple requests with fewer than 10 bookings each.

Yes, after correction

10080

Update refused. Booking ID cannot be found

A booking ID that cannot be accessed by the API was requested. Verify the booking ID and log on to Partner Central for more information about the booking.

Note: Bookings will be removed from the API system 8 days after the traveler's departure and will no longer be available for electronic retrieval or confirmation.

Yes, after correction

10081

Update refused. Hotel ID and Booking ID mismatch: the Hotel ID specified in the Booking Confirmation request doesn't match with the property this booking belongs to

Verify the Booking ID/Hotel ID mapping information. If this looks good, and the error recurs, validate the behavior of your system.

Yes, after verification

10100

Update refused. The specified booking type does not match the one Expedia Group has stored for this booking ID in our system

Make sure the booking ID specified in the request message is the one requiring confirmation. The booking type that should be sent with the booking ID can be found in the Booking Retrieval response message.

If this does not work, please verify your implementation of the API.

Yes, after verification

10101

Update refused. Confirmation for bookings must be sent no more than 8 days after traveler departure, which for this booking was on (date).

Verify that the booking ID specified in the Booking Confirmation request message is correct.

If this does not work, please verify the partner's implementation of the API.

Yes, after verification

10102

Booking confirmation refused for booking because a newer version of this booking is awaiting retrieval.

Issue a Booking Retrieval request to return the newest version of the booking, then send the newest confirmation number for the booking.

This confirmation should either be discarded if it's become irrelevant due to the change awaiting retrieval, or resent after the Booking Retrieval has been performed.

Yes, after correction

10103

Booking confirmation [confirmation number] refused for booking [booking ID] because this booking has already been confirmed 3 times. Any subsequent confirmation will be refused.

Only 3 different confirmation numbers can be sent for one booking instance (where “booking instance” is defined as one version of the booking. Every modification or cancellation is considered a different instance).

Only send confirmation numbers once per booking instance, or any time the actual property confirmation number changes.

Yes, after correction

10105

Update refused. Internal system error, please try again in a few minutes for this booking.

Please retry. Confirmation number may not have been stored.

Yes