ReferenceAvailability and Rates API

Error messaging

Error messaging in the Availability and Rates API helps you understand why a rate or availability request is denied. When this element appears, nothing included in the Availability and Rates request was processed. One or more instances of this element appear if the request failed.

The following element provides an error code instead of a success or warning if an error occurs.

Error element

Occasionally errors are encountered when developing and trying to connect to the Availability and Rates API. This element contains any error codes returned.

This element cannot be present at the same time as the <Success> node. Error text may be up to 1024 characters per error.

For a comprehensive list of error codes and troubleshooting tips, please refer to the Testing and Troubleshooting section.

1<?xml version="1.0" encoding="UTF-8"?>
2<!--Sample error message, in case the property either made a mistake while mapping -->
3<AvailRateUpdateRS xmlns="namespace"
4 xmlns:xsi="schema">
5 <Error code="{integer}">error message</Error>
6</AvailRateUpdateRS>

Child elements

Name

Description

@code

Error codes are defined by Expedia Group for specific errors. Data type: integer, between 1000 and 8000

Availability and Rates response: errors

The following is a sample error response message: in this case the property made mistakes in its room type ID and its rate plan ID in the Availability and Rates request message.

1<?xml version="1.0" encoding="UTF-8"?>
2<!--Sample error message, in case the property either made a mistake while mapping -->
3<AvailRateUpdateRS xmlns="http://www.expediaconnect.com/EQC/AR/2007/02"
4 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
5 <Error code="3203">The following RoomTypeIDs do not belong to the given property: 432432.</Error>
6 <Error code="3204">The following RatePlanIDs do not belong to the given property: 234543.</Error>
7</AvailRateUpdateRS>
Error codes and descriptions

For additional details, see the error descriptions in the Testing and Troubleshooting section.

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

2002

Parsing error: parsing_error_description

Correct XML format to comply with Expedia Group's specification. Developers of your systems 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

3015

Business validation error including (but not limited to) the following:

  • No updates provided inICPRUpdateMessage
  • MaxLOS value (X) smaller than the MinLOS value(Y)
  • The NumberOfGuests attribute may not be 0

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

3020

Validation error: start date must not be before yesterday

Verify the date. Make sure the system cannot send a date in the past and drop this message (no retry).

No

3021

Validation error: end date must not be before the start date.

Make sure the system cannot send an end date smaller than a start date, and drop this message (no retry).

No

3022

Validation error: end date must be within 2 years range.

Make sure that the end date of a date range cannot be greater than today + 2 years, and drop this message (no retry).

No

3026

Flexible and total allocation cannot be sent together for roomType.

Make sure that the system cannot generate an Availability and Rates request which specifies both flexible allocation and total allocation available for a room type.

No

3090

Pricing models mismatch: you tried to update a price for one pricing model, but your property is configured to use a different one.

Review your implementation of the API and make sure the pricing model you use is in line with what is configured in Partner Central for your property.

Yes, after correcting pricing model

3103

Currency code mismatch.

Make sure the property is sending the same currency as the one configured in Partner Central for this property.

The property should send the same currency as the one configured in Partner Central for this property.

Yes, after correcting currency code

3107

Update exceeds allowable size - Maximum allowable size is 5000 updates

The message contains too many different updates. Expedia Group limits the number of distinct updates in one message to 5000.

Please refer to Sending updates to Expedia and its sub sections for detailed information about Expedia Group recommendations for maximum number of updates per message.

Yes, after correction

3108

Duplicate Updates in the same message – [exact nature of conflicting updates received in request]

The message sent contains the same product and dates twice or more, and the updates requested conflicts with one another. Please make sure to only send rates, restrictions or availability updates for a product and stay date combination once in a message.

Yes, after correction

3123

Length of stay must be provided for the rate plans with LOS enabled

The message didn't include the <Rate>/@lengthOfStay attribute for a rate plan that is length of stay pricing enabled. Review your implementation of the API and make sure the pricing model you use is in line with what is configured on the HotelExtranet for your property.

Yes, after correction

3124

Length of stay attribute can only be set on Rate Plans with LOS enabled

The message included the <Rate>/@lengthOfStay attribute for a rate plan that is not length of stay pricing enabled. Review your implementation of the API and make sure the pricing model you use is in line with what is configured in Partner Central for your property.

Yes, after correction

3125

Field not accessible for edit for this property and source - [Exact field not accessible]

The message sent contains updates that cannot be accepted for the property specified.

The sources may vary:

Rate change edit not allowed: the rate change indicator is used in request but product isn't enabled for day of arrival pricing.

Please correct the problem in the message.

Yes, after correction

3128

Invalid data in request

Yes, after correction

3129

Invalid Date

Verify the dates you provided in the Availability and Rates request and then resubmit your message.

Yes, after correction

3135

MinLOS value ([value provided in RQ]) exceeds Extranet auto-approval threshold ([Expedia configuration]) for length of stay

A MinLOS restriction value greater than the acceptable threshold defined for your property in Expedia Group's system was submitted.

Please resubmit your update with a smaller value, or contact your market manager.

Yes, after correction

3142

Rate plan does not match the property acquisition type - Rate plan XXX does not match acquisition type

You provided an update for a derived/non-manageable rate, which is not allowed.

For more information about flex rate plans and derived/non-manageable rates, please refer to the Send the right type of rate to Expediasection

Yes, after correction

3145

Not available for updates. Property undergoing business model conversion.

Verify if the property has completed business model conversion for Expedia Traveler Preference (ETP) and resubmit updates.

Yes, after verification

3202

Property ID not found. Either an invalid 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 system has access to update this property (i.e. the user is able to access this property through Partner Central).

Yes, after verification

3203

The following RoomTypeIDs do not belong to the given property: room_type_ID

Fix mapping in your system.

Yes, after correction

3204

The following RatePlanIDs do not belong to the given property : rate_plan_ID

Fix mapping in your system. If you are building new products, the Market manager must be notified ahead of time to create the new product in Expedia Group's systems.

Yes, after correction

3210

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

A lock error occurred at the daily data layer. You tried to perform more than one simultaneous requests against the same product and date. For any given product on a particular day, do not attempt to send 2 concurrent messages. Always wait for a message to be responded by Expedia before sending any subsequent message.

Yes, after closing the other connection

3405

Message size limit exceeded.

The overall size of the Availability and Rates incoming request exceeds our limit of 100 kb. You need to break down the request into smaller messages.

Yes, after correction

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

Expedia Group 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

7000

Default warning

Covers use cases that are not defined below. Refer warning description for specific warning details.

Maybe (refer to warnings)

7009

Occupancy exceeds maximum allowed value

Applicable to occupancy-based pricing properties only. You tried to update an occupancy level that exceeds the room's maximum occupancy defined in Expedia Group's system.

Yes, after correction

7010

Room type cannot be closed because there is base allocation remaining on the room.

The room type will remain available on Expedia Group until all base allocation is sold.

For assistance, please contact your market manager, who will manage the process internally or correct the issue.

No

7013

Total Inventory Available cannot be less than the current base allocation value (XX).

In the case of a property using base allocation, Total Inventory Available cannot be set to a value less than the current base allocation room count.

Yes, after correction

7014

At least one standalone rate plan should be kept open until all base allocation has been sold.

The last available rate plan of the standalone rate category has to remain open until all base allocation has been sold.

For assistance, please contact your market manager, who will manage the process internally or correct the issue.

Yes, after correction

7016

MaxLOS value (value provided) smaller than the MinLOS value (value provided).

This problem will occur if a MinLOS restriction received in an incoming Availability and Rates request is greater than existing MaxLOS restriction already stored in Expedia Group's system for this property. You must make sure to provide a MinLOS value smaller than MaxLOS. Note that if you include within the same Availability and Rates request a MinLOS > MaxLOS, an error will be returned.

Yes, after correction

7018

Base Availability request adjusted to prevent total availability from exceeding the system maximum

Only applicable to properties on base allocation and for updates made using “flexibleAllocation”. If the total of base and flexible allocation exceeds Expedia Group's hard limit of 4999, this error will be returned.

In this specific case, the update was processed and the total allocation is adjusted to 4999 automatically.

Note that it is not possible to provide flexible or total allocation greater than 4999 in Availability and Rates requests, as the schema does not allow it. This warning is returned solely when there is base allocation left in Expedia Group systems, and the addition of base plus the value provided in Availability and Rates request exceeds 4999.

Yes, after correction

7019

Net rate must be within Rate Verification threshold.

As per Expedia Group rate validation & verification rules (based on recent bookings), the rate provided is either too high or too low. Please correct the rate value.

Yes, after correction

7021

Sell/lowest available rate must be within Rate Verification threshold.

As per Expedia Group rate validation & verification rules (based on recent bookings), the rate provided is either too high or too low.

Yes, after correction

7022

Inactive Rate Plan Updated.

The update was processed; however this product will not be sold until an Expedia Group Market Manager activates this product.

No

7023

Restrictions were not updated due to a rate plan linkage rule. Only Main rate plans, not Derived rate plans, can receive restrictions updates.

An active rate plan linkage rule exists, that links the restrictions between the rate plan provided in the request and a parent/main rate plan. It is not possible to update a child/derived rate plan.

Yes, after correction

7024

Rates were not updated due to a rate plan linkage rule. Only Main rate plans, not Derived rate plans, can receive rates updates.

An active rate plan linkage rule exists, that links the rates between the rate plan provided in the request and a parent/main rate plan. It is not possible to update the child/derived rate plan.

No

7025

Net rate must be within Rate Verification threshold. The rate plans (listed) with the violation and their Main/Derived rate plans (not listed) are not updated.

An active rate plan linkage rule exists between the rate plan provided in the request and a parent/main rate plan.

The net rate update we received was outside of the rate verification threshold defined for either the parent/main rate plan, or the child/derived rate plan. The net rates of both the parent/main and child/derived rate plans were not updated.

This warning is equivalent to 7019 (used for unlinked rate plans).

Yes, after verification

7026

At least one rate plan should be kept open until all base allocation has been sold. The rate plans (listed) with the violation and their Main/Derived rate plans (not listed) are not updated.

An active rate plan linkage rule exists between the rate plan provided in the request and a parent/main rate plan.

The Availability and Rates request attempted to close either the last open parent/main rate plan, or the child/derived rate plan, but there was base allocation left. The availability statuses of both the parent/main and child/ derived rate plans were not updated.

This warning is equivalent to 7013 (used for unlinked rate plans).

Yes, after verification

7027

Sell rate must be within the Rate Verification threshold. The rate plans (listed) with the violation and their Main/Derived rate plans (not listed) are not updated.

An active rate plan linkage rule exists between the rate plan provided in the request and a parent/main rate plan.

The sell rate update we received was outside of the rate verification threshold defined for either the parent/main rate plan, or the child/ derived rate plan. The sell rates of both the parent/main and child/ derived rate plans were not updated.

This warning is equivalent to 7021 (used for unlinked rate plans).

Yes, after verification

7028

We weren’t able to identify the tax rate included in your recent updates. Please make sure that you have correctly calculated the tax rate for the base price.

Due to a goods and services tax (GST) in India, partners with properties in India must avoid uploading tax-inclusive rates that fall into the ranges defined on this page: https://apps.expediapartnercentral.com/lodging/help/help-article/rooms-and-rates/rates-and-availability/about-tax-inclusive-rate-errors.

No