ReferenceProduct API

Error messaging

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}

Property Name

Type

Description

code

integer

Full list of error codes.

message

string

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
LevelError codeError descriptionError explanationRecommended action
Auth1000Access denied: your account is not authorized to manage this property.API Account is either not attached to the property or there is a cache delay on Expedia's end.Contact Expedia Central Ops team (Engagement and Integration) to confirm that Master User is attached to the property.
Auth1001Missing or Invalid Username or Password.Master User either does not have correct password in place, is not attached to the property or there is a cache delay on Expedia's end.Contact Expedia Central Ops team (Engagement and Integration) to confirm that Master User is attached to the property. If Expedia confirmed that the user is attached yet the error persists, confirm internally that password was not changed.
Auth1003Access to this API with a non-API account is forbidden. Please use an API account.
Generic2002There is a problem with the submitted payload. Please make sure it's a valid JSON message.This error means that the format of Product API Request message is incorrect.Please contact your DEV/TECH team to confirm JSON formatting.
Generic2003The property or element [] is or contains data that is invalid/unrecognizable in this model.This error means that the format of Product API Request message is incorrect.Please contact your DEV team to confirm specified element against Expedia Public specification.
Generic2004Invalid format: details.This error means that the format of Product API Request message is incorrect.Please contact your DEV/TECH team to confirm JSON formatting.
Generic2404Resource not found: the server has not found anything matching the Request-URI.This error means that the endpoint used by Product API to connect to Expedia is incorrect.Please contact your DEV team to verify the endpoint used in Product Automation; Contact Central Ops Integration team to confirm the correct URL
Generic2405Method not allowed: the method specified in the Request-Line is not allowed for the resource identified by the Request-URI. Allowed method(s):[]This error means that the action (create, read, modify) is not supported.Verify if it occurred on Create or Modify; Verify if occurred on Room, Rate or Room amenities;
Generic2406Requested response media type unsupported: the resource identified by the request is unable to generate response entities of the media type requested by the Accept header attribute in the request.This error means that the media type on the response message is unexpected/unsupported.Please contact your DEV team to verify configuration for Product Automation; Contact Central Ops Integration team to confirm the correct format.
Generic2407The HTTP header field "Accept" with value "text/html, application/rss+xml, application/atom+xml, text/xml, text/rss+xml" could not be parsed.Please contact your DEV team to verify configuration for Product Automation; Contact Central Ops Integration team to confirm the correct format.
Generic2415Request media type unsupported: the server is refusing to service the request because the media type specified in request under the Content-Type header attribute is not supported by the requested resource for the requested method.This error means that the media type on the request message is unexpected/unsupported.Please Contact your DEV team to verify configuration for Product Automation; Contact Central Ops Integration team to confirm the correct format.
Generic2420Element <element name> has to be a valid date formatted as YYYY-MM-DD.This error means that one of the elements that require date ranges (Extra Person Fees, Booking/Travel Window, Service Fee, etc) utilizes incorrect/unsupported date format
Generic2421Element <element> name has to be an integer.This error occurs when specified value is not a full number. This error could occur for various elements.Adjust specified in the error description element to be a full number.
Generic2422Element <element name> has to be a double.
Generic2423Invalid boolean value for element <element name>, has to be true or false.
Generic2424Invalid value <> for the element <>This error indicates that an unsupported value has been included on an element that requires a specific list of values.Ensure that the value specified for the element mentioned in the error response is one supported by Expedia.
Generic2425Invalid CORS request.
Generic2426Value null can not be specified in Array: <element name>.This error indicates that blank value has been included on an element that requires a specific list of values.Ensure that the value specified for the element mentioned in the error response is one supported by Expedia
Generic2993The API cannot be used for properties on per person pricing.
Generic4000Internal system error, please try again in a few minutes.This error can occur both on rate level and room level mapping, and can be due to various factors.Contact Expedia Central Ops team for Integration specialist to verify internal logs and confirm the source of error, advising you on the further actions.
Generic4002Internal system error, please try again in a few minutes.This error can occur both on rate level and room level mapping, and can be due to various factors.Retry request, if still seeing an error contact Expedia Central Ops team for Integration specialist to verify internal logs and confirm the source of error, advising you on the further actions.
Generic4100Internal System Error. Do not retry this request. Our support team was notified of the problem.This error can occur both on rate level and room level mapping, and can be due to various factors.Contact Expedia Central Ops team for Integration specialist to verify internal logs and confirm the source of error, advising you on the further actions.
Property3102Limit must be a number between 1 and 200This error occurs on GET (READ) requests only for the properties associated with Product API Account. Limit refers to the number of returned properties. Therefore, this error occurs when limit is below 0 or above 200.Ensure that the read request is set for less than 500 properties.
Property3103Offset must be a number greater or equal to 0
Property3104Offset exceeds total number of properties that meet the search criteria.This error occurs on GET (READ) requests only for the properties associated with Product API Account. Limit refers to the number of returned properties, this error occurs when offset exceeds the number of properties associated with the account.Ensure that the read request is set for the number of properties that does not exceed the total number of properties associated with Product API account.
Property3901Invalid status value: <>This error occurs on GET (READ) requests only for the properties associated with Product API Account. "Status" element can only be set to "all". Therefore, this error occurs when "status" is set any other value but "all".
Property3202Property not found. You specified a Property ID that does not exist or is inactive.This error occurs when request (READ, CREATE or MODIFY) is submitted with incorrect EID.Please contact Central Ops Engagement specialist to confirm Expedia ID for the affected property.
Rate Plan3300Unable to create rate plan, contract not available.This error occurs on the Properties connected via Product but not Property API when there are no active rate plans. For the properties connected on Product API only, first rate plan should be created manually as compensation is attached based on the last active rate plan of the specific type (Standalone, Package or Corporate).Contact Expedia or Create one rate plan manually for each rate plan type (Standalone, Corporate, Package).
Rate Plan2996Only Expedia Traveler Preference rate plans can be created for this propertyThis error occurs only on properties set to Expedia Traveler Preference (ETP) and occurs when Standalone or Corporate rate plans are being created as ExpediaCollect or HotelCollect only.Ensure that failed rate plan is set as Expedia Traveler Preference (i.e. has Expedia Collect and Hotel Collect models).
Rate Plan3026Age category [] is currently not defined as supported by your property. If you feel you got this error by mistake, please contact Expedia to resolve.This error is caused by the Age Category disparity between the room and its property settings.Contact Expedia Central Ops team (Engagement) to adjust Age Categories at Property Level.
Rate Plan3028Unsupported value add inclusion <value> for rate plan of type <rate plan type>This error occurs when Corporate-only Value Adds are sent on the Standalone/Package rate or the other way around.Please consult Value add inclusions enumeration to verify which Rate Level Value adds are accepted for Standalone/Package rate and which Value Adds are accepted for Corporate rate. Access rate level setting and adjust Value Add.
Rate Plan3029The limit of <limit> Value Add Inclusions has been exceededOn Expedia, each rate plan is allowed only 3 Value Adds.Access rate level setting and adjust Value Add.Please consider utilizing some of the room amenities.amenityCodes
Rate Plan3030Incorrect setting provided in your input request: the requested rate plan configuration ("TaxInclusive=false") doesn't match with the configuration of your property in Expedia system (TaxInclusive=true). If this is not an error from your part, please contact Expedia to address this issueThis error occurs for Properties on rate acquisition type = SellLAR. On SELL properties, Tax Inclusivity is configured both on property and product level (on NET properties, only on rate level). Therefore, pushed rate plan should have the same Tax Inclusivity status as property at Expedia.Verify results of PROPERTY READ (GET) message (taxInclusive will be listed as True).Ensure that rate plan level tax inclusivity is enabled.
Rate Plan3031AdditionalGuestAmounts should have at least one AdditionalGuestAmount defined.This error occurs when "AdditionalGuestAmounts" (i.e. Extra Person Fees) collection is included in the message without any values.However, if this error occurs, please contact your DEV/Tech support.
Rate Plan3032Missing age category on <count> age category(ies). It has to be set to 'Adult', 'ChildAgeA', 'ChildAgeB', 'ChildAgeC', 'ChildAgeD' or 'Infant'This error occurs when Extra Person Fees collection includes the value but does not specify the age category for said value.Access rate level settings and adjust Extra Person Fee to be specify age category for every defined fee.
Rate Plan3033AdditionalGuestAmount value must be between0.000 and 12000000.000 inclusively, with up to 3 decimal places.This error occurs when the value set for Extra Person Fees is outside of the allowed by Expedia range.Access rate level settings and adjust Extra Person Fee to be within the allowed range and decimal count.
Rate Plan3034AdditionalGuestAmount must provide both start and end dates if the date range is providedThis error occurs when the date range for the Extra Person Fees is specified incorrectly.Access rate level settings and adjust Extra Person Fee to have both start and end date.
Rate Plan3035End date is not after start date for AdditionalGuestAmountThis error occurs when the start date for Extra Person Fees is set after the end date.Access rate level settings and adjust Extra Person Fee to have both start and end date.
Rate Plan3036AdditionalGuestAmount computed Sell-Rate value exceeds max allowed value of 12000000.000. Sell Rate value is computed by adding compensation to the net rate provided.
Rate Plan3037Element distributionRules[].expediaId cannot be specified in a create request.distributionRules[].expediaId is Expedia Rate Plan ID and cannot be included in the CREATE messages.Verify if the intended action is CREATE or UPDATE. Verify if Expedia Rate ID is stored in the system. Verify if the rate plan already exists under the specified room.— If CREATE message was intended (rate does not exist under the specified room):Please verify with your DEV/TECH team why Rate ID is included in the CREATE message.— If MODIFY message was intended (rate does exist under the specified room):Please verify with your DEV/TECH team why CREATE message was sent instead of MODIFY.
Rate Plan3037Element <element name> cannot be specified in a create request.Certain elements (URL, compensation, manageable, etc.) are generated after rate is created and cannot be included in the CREATE message, only in UPDATE.Verify if the intended action is CREATE or UPDATE. Verify if Expedia Rate ID is stored in the system. Verify if the rate plan already exists under the specified room.— If CREATE message was intended (rate does not exist under the specified room):Please verify with your DEV/TECH team why Rate ID is included in the CREATE message.— If MODIFY message was intended (rate does exist under the specified room):Please verify with your DEV/TECH team why CREATE message was sent instead of MODIFY.
Rate Plan3037Element resourceId cannot be specified in a create request.This error occurs when CREATE message includes a rate plan ID, which means that (1) either CREATE is sent instead of the MODIFY or (2) ID of an already existing Rate Plan was included in the message.Verify if the intended action is CREATE or UPDATE. Verify if Expedia Rate ID is stored in the system. Verify if the rate plan already exists under the specified room.— If CREATE message was intended (rate does not exist under the specified room):Please verify with your DEV/TECH team why Rate ID is included in the CREATE message.— If MODIFY message was intended (rate does exist under the specified room):Please verify with your DEV/TECH team why CREATE message was sent instead of MODIFY.
Rate Plan3038AdditionalGuestAmount percent must be between0.000 and 1.000 inclusively, with up to 3 decimal places.This error occurs when Extra Person Fees are set as percentage and the value is passed as % instead of the decimal: 50 (or 50%) instead of 0.5.If this error is encountered, please contact your DEV/TECH support.
Rate Plan3039Only one of 'Percent' and 'Amount' can be specified for additionalGuestAmounts for a particular age category.This error occurs when Extra Person Fee has both amount and percentage set up for the same age category.
Rate Plan3040AdditionalGuestAmount date ranges cannot overlap for the same age category.This error occurs when multiple Extra Person Fees are configured for the same age category, varying per date range.However, date ranges overlap.Ensure that the date ranges do not overlap.
Rate Plan3057Rate Plan name [] contains more than the maximum number of characters: 40.This error occurs when the rate plan name exceeds limitation set by Expedia (40 characters).Adjust rate plan name to be 40 characters or less.
Rate Plan3060Value add inclusion not provided
Rate Plan3063Missing Cancel Policy
Rate Plan3065Cancel Policy must specify 1 or 2 default penalties.This error occurs when no cancellation policy is selected yet 'cancelPolicy' node is included in the message.If this error is encountered, contact your DEV/TECH team.
Rate Plan3066Missing Penalty
Rate Plan3067Deadline must be a number between 0 and 32767This error occurs when deadline (i.e. cancellation window) is set to be more than 32767 hours (approximately 1365 days).Adjust cancellation window to be less than 32767 hours.
Rate Plan3068Missing cancel policy penalty perStayFeeThis error occurs when rate plan message includes cancelPolicy but does not include perStayFee element. perStayFee can remain undefined and passed to Expedia as "none"; however, it cannot be omitted.However, if this error is encountered, contact your DEV/TECH team.
Rate Plan3069Cancel policy exception dates for different exceptions cannot overlap. Exception with startDate [] overlap with exception having startDate [].This error occurs when cancellation policy with exceptions is used. This error occurs when cancellation policy exceptions overlap.If this error occurs, ensure that cancellation exceptions do not overlap.
Rate Plan3070Cancel policy exception dates with endDate in the past cannot be provided. Cancel policy exception with endDate [null] should be changed or removed.This error occurs when cancellation policy was defined in the past and the update/create message does not translate the dates into the present range. Expedia does not allow creation of the rate plan with outdated cancellation policy exception.Access Cancellation Policy Settings.Ensure that cancellation policy exception applied to the rate plan in question is set to cover a present date range or remove outdated exception for the rate.
Rate Plan3071Missing mandatory element: distributionRules[].expediaIdThis message occurs when Expedia ID (i.e. rate plan ID) is missing from the update (PUT) message.Verify request message to see if rate plan ID is listed for both EC and HC pieces (if ETP rate). If not, perform a READ (GET) action and ensure that Rate Plan Exists and Rate ID is stored. If rate plan ID is not stored in your system and continuously is not included in the modify message:— Attempt to delete the rate plan and re-create.— Please notify your TECH/DEV team. If rate plan does not exist, send CREATE instead of the MODIFY.
Rate Plan3071Missing mandatory element: distributionRules[].compensationThis error occurs on rate update message done in full overlay mode (PUT).When using full overlay mode (PUT), all information listed in read (GET) message should be returned with adjustments.Compensation is returned in read (GET) message. Compensation should not be adjusted.Therefore, this message occurs when Compensation is missing from the update (PUT) message.Verify request message to see if rate plan compensation is listed for both EC and HC pieces (if ETP rate). If not, perform a READ (GET) action and ensure that Rate Plan Exists. If compensation continuously is not included in the modify message:— Attempt to delete the rate plan and re-create.— Please notify your TECH/DEV team. If rate plan does not exist, send CREATE instead of the MODIFY.
Rate Plan3072Unsupported modification to element "attribute"This message occurs when a change is made to an attribute that cannot be modified via the API.Verify request message to ensure you provide the same value for these as you received in the GET Response.
Rate Plan3073Too many cancel policy exceptions included (null). Maximum number of exceptions supported is 500.This error occurs when cancellation policy includes more than 500 cancellation exception ranges.Each range is defined by the start and end date.Please see error 3075 for the details of Cancellation Policy application Logic.Ensure that 500 exception ranges or less are set up for the failed rate.
Rate Plan3074End date is not after start date for CancelPolicy exceptionThis error occurs when cancellation exception range is out of order: end date precedes start date.Ensure that Date Range of cancellation policy is in chronological order.
Rate Plan3075Exactly one penalty with deadline 0 should be provided in cancel policy default penalties listThis error occurs when Cancellation Policy does not specify "Inside Policy Window". Expedia always requires inside window policy (“deadline” set to 0) to be specified. When only “deadline” set to 0 is listed, the same penalty will be applied to the inside and outside window.Please contact your DEV/TECH team.
Rate Plan3076Cancellation policy amount (<amount>) must be greater or equals to 0.000 with a maximum of 3 decimals.
Rate Plan3077Exactly one penalty with deadline 0 should be provided in each cancel policy exceptionPlease see 3075 for the cancellation policy application logic.This error is caused by the same issue as in 3075 just occurring in "exceptions" instead of "default".If this error is encountered, contact your DEV/TECH team.
Rate Plan3078Missing Distribution Rule Distribution ModelThis error occurs when "partnerCode" (i.e. rate plan code) is specified in the message, however, its "distributionModel" (i.e. Business Model) is not specified.Distribution Rule (a.k.a. Business Model) refers to Hotel or Expedia Collect model of the rate plan.On Expedia, Rate Plan cannot exist without having Distribution Rule associated with it.Ensure that Distribution (Business) model of the rate plan is specified.
Rate Plan3079Cancel Policy exceptions must specify 1 or 2 penalties.Please see 3065 error. This error is caused by the same issue as in 3065 just occurring in "exceptions" instead of "default". P lease see 3075 for the cancellation policy application logic.If this error is encountered, contact your DEV/TECH team.
Rate Plan3080Rate plan must specify a Distribution Rule.Distribution Rule (a.k.a. Business Model) refers to Hotel or Expedia Collect model of the rate plan.On Expedia, Rate Plan cannot exist without having Distribution Rule associated with it.Therefore, this error occurs when the rate plan is being created or updated (in full overlay mode) without Distribution Rules in place.Ensure that Distribution (Business) model of the rate plan is specified.
Rate Plan3081Rate plan distribution model does not match the property's distribution modelThis error occurs when rate plan model is not allowed per the property settings.Contact Expedia CentralOps Engagement specialist to confirm Property Distribution (a.k.a. Business) model.
Rate Plan3082Duplicate Distribution Model not accepted.This error can only occur on properties set to ExpediaTravelerPreference. This error occurs when rate plan has two codes defined with the same distribution model.Ensure that Distribution (Business) model of the rate plan is specified in a way that Expedia Collect and Hotel Collect are listed once.
Rate Plan3084Expedia Collect partner code is required and must not exceed <element name> charactersThis error occurs when rate is being created without rate plan code.Ensure that rate plan code is defined for the rate in question.
Rate Plan3085Hotel Collect partner code is required and must not exceed <element name> charactersThis error occurs when rate is being created without rate plan code.Ensure that rate plan code is defined for the rate in question.
Rate Plan3086Occupants for base rate can only be set for PerDayPricing rate plans, and its value should be greater than 0 and less than the room's maximum occupantsFor properties with Per Day Pricing, Occupants for base rate define the occupancy levels in the rate - remaining occupancy level would require Extra Person Fee.Therefore, "Occupants for base rate" can only be used for Per Day Pricing properties.Therefore, this error occurs when this setting is used on the property with Occupancy Based Pricing.Verify Pricing Model of the property to ensure that it is correct (perform Property READ (GET)); Verify Pricing Model of the rate plan;— If Property should be Per Day Pricing, adjust Pricing model of the rate; If Property should be Occupancy Based, remove "occupants for base rate".
Rate Plan3087Rate Plan Partner code <element name> contains unsupported character(s). Accepted characters are a-z, A-Z, 0-9, ., _, and -.This error occurs when rate plan code utilizes unsupported characters (special characters).Ensure that rate plan code utilizes only characters indicated in the Error Description.
Rate Plan3088Expedia Traveler Preference (ETP) requires the manageable flag being set to the <distribution model> Distribution Rule
Rate Plan3090ExpediaCollect and HotelCollect Rate plans must define only one distribution rule. Expedia Traveler Preference Rate plans require two: one of each distribution modelThis error occurs only on properties set to Expedia Traveler Preference.This error only occurs when more than two rate plan codes are listed in the rate plan message. On Expedia, rate plans are only allowed to have up to two codes: one set to Expedia Collect and one - to Hotel Collect.Including 3rd rate plan code for the same rate with the duplicated distribution rule will trigger such error.Ensure that only two rates are paired for the rate plan in question.If that's the case, contact your DEV team.
Rate Plan3091Current rate plan distribution model is ExpediaCollect and HotelCollect and cannot be modifiedThis error occurs when distribution model of the rate is being modified by the Product API call.Modifications of the distribution model are not supported via Product Automation.Verify if rate plan is PAIRED or EC only in CRS/PMS; Contact Expedia Engagement specialist to confirm that distribution model (a.k.a. business model) in Expedia matches CRS
Rate Plan3092Current rate plan distribution model is ExpediaCollect and cannot be modifiedPlease see 3091.Please see 3091.
Rate Plan3093Compensation provided in request does not correspond to your property contract.This error occurs when compensation is included in the message and does not match Property's contract. Compensation should not be included in POST (Create) message at all. When compensation is included in PUT (Modify) call, ensure the value is the same as that returned in GET(Read) response.If this error is encountered, contact your DEV/TECH team.
Rate Plan3094Compensation percent is required and must be equal to or greater than null and smaller than 0.99.Occurs on a request message when the "compensation" object is included with the "percent" key/value pair omitted. Compensation should not be included in POST (Create) message at all. When compensation is included in PUT (Modify) call, it should return the same value included in GET(Read) response.If this error is encountered, contact your DEV/TECH team.
Rate Plan3095Compensation minAmount must be greater or equal to 0 for ExpediaCollect distribution model and must be empty for HotelCollect distribution model.Occurs on a request message within the "compensation" object. Related to minAmount being included with a value on distributionModel": "HotelCollect", or minAmount value missing on distributionModel": "ExpediaCollect". Compensation should not be included in POST (Create) message at all. When compensation is included in PUT (Modify) call, it should return the same value included in GET(Read) response.If this error is encountered, contact your DEV/TECH team.
Rate Plan3096Compensation exception dateStart is required.Occurs on a request message within the "compensation" object. Related to "exceptions" being sent without including "dateStart" in the array of values. Compensation should not be included in POST (Create) message at all. When compensation is included in PUT (Modify) call, it should return the same value included in GET(Read) response.If this error is encountered, contact your DEV/TECH team.
Rate Plan3097Compensation exception dateEnd is required and must not be prior to dateStart.TOccurs on a request message within the "compensation" object. Related to "exceptions" being sent without including "dateEnd" in the array of values, or including "dateEnd" with a date value earlier than then the one included for "dateStart". Compensation should not be included in POST (Create) message at all.When compensation is included in PUT (Modify) call, it should return the same value included in GET(Read) response.If this error is encountered, contact your DEV/TECH team.
Rate Plan3098Compensation exception percent is required and must be between 0 and 1.0.See error 3094. Error 3098 occurs because of the same behavior as in 3094 when it occurs in "exceptions" collection instead of the default.If this error is encountered, contact your DEV/TECH team.
Rate Plan3099Compensation exception minAmount must be greater or equal to 0 for ExpediaCollect distribution model and must be empty for HotelCollect distribution model.See error 3095.Error 3099 occurs because of the same behavior as in 3094 when it occurs in "exceptions" collection instead of the default.If this error is encountered, contact your DEV/TECH team.
Rate Plan3100Compensation exception day of week: 'day' is required and must be 'true' or 'false'.Occurs on a request message within the "compensation" object. Related to "exceptions" being sent without including values for all 7 days of the week. Compensation should not be included in POST (Create) message at all.W hen compensation is included in PUT (Modify) call, it should return the same value included in GET(Read) response.If this error is encountered, contact your DEV/TECH team.
Rate Plan3101Compensation exception date ranges must not overlap.Occurs on a request message within the "compensation" object. Related to "exceptions" being sent with date values that overlap. Compensation should not be included in POST (Create) message at all. When compensation is included in PUT (Modify) call, it should return the same value included in GET(Read) response.If this error is encountered, contact your DEV/TECH team.
Rate Plan3105Invalid Room Type/Rate Plan association specified. Rate Plan ID [] does not belong to room type ID []; it belongs to room type ID [].This error occurs when Expedia Rate Plan ID stored in CRS/PMS Mapping Table does not belong to the Expedia room type ID stored in CRS/PMS mapping tableTrigger a FETCH to update CRS Mapping table with accurate Expedia IDs. Verify that ID was updated for the product in question. Trigger MODIFY. If this did not help, contact Expedia Engagement specialist to confirm product IDs.
Rate Plan3106Element minLOSDefault has to be a number between 1 and 28.Expedia does not support Length of Stay longer than 28 nights.Length of stay should be defined by the full number (i.e. without decimals).Therefore, this error occurs when minimum Length of Stay setting is set to 0 or 29+.Adjust minimum Length of Stay to be the value between 1 and 28.
Rate Plan3107Element maxLOSDefault has to be a number between 1 and 28.Expedia does not support Length of Stay longer than 28 nights.Length of stay should be defined by the full number (i.e. without decimals).Therefore, this error occurs when maximum Length of Stay setting is set to 0 or 29+.Adjust maximum Length of Stay to be the value between 1 and 28.
Rate Plan3108minLOSDefault cannot be greater than maxLOSDefault.Expedia does not support Length of Stay longer than 28 nights.Length of stay should be defined by the full number (i.e. without decimals).Therefore, this error occurs when minimum Length of Stay exceeds maximum Length of Stay.Adjust minimum and/or maximum Length of Stay for the minimum LOS to be smaller than maximum LOS.
Rate Plan3110You reached the maximum number of active rate plans for your property.On Expedia, by default, property can have up to 200 active rates.This error occurs when Create attempt is sent to 201 rate.Inactivate or Delete unused rates (removed their association to Expedia Channel). If all rates must remain active, contact CentralOps Engagement specialist to increase product limit.
Rate Plan3111Rate plan cannot be deleted because it is the child of rate plan [parent rate plan id].This error only occurs on the properties utilizing Rate Plan Linkage.Each Rate Plan Linkage requires one parent rate and at least one child rate.In this pairing, child rate is in sync with the parent rate and therefore cannot be deleted first.Deactivate parent rate to deactivate child. If only child rate should be removed, contact Expedia to disable rate plan linkage, and then send delete the rate in question.
Rate Plan3112Rate plan cannot be updated because it is the child of rate plan [], and must be kept in sync with it. To make change to this rate plan, modify its parent and changes will be cascaded down automatically.This error only occurs on the properties utilizing Rate Plan Linkage.Each Rate Plan Linkage requires one parent rate and at least one child rate.In this pairing, child rate is in sync with the parent rate.Modify parent rate to modify child.
Rate Plan3204Rate plan ID not found. You specified a rate plan ID that does not exist for this property.Similarly to the error 3105, 3204 is triggered when rate plan Expedia ID is stored in CRS/PMS mapping table under an incorrect, in this case, hotel.For instance: in CRS/PMS, hotel code ABC has rate DEF; In Expedia, hotel code ABC got assigned ID 123 and rate DEF under this hotel got assigned ID 456. However, in CRS/PMS mapping table, ID 456 got saved for rate DEF under the hotel XYZ which has an ID 789. Therefore, update call is sent to hotelID-789/roomID1/rateID-456 instead of hotelID-123/roomID2/rateID-456.Trigger a FETCH to update CRS Mapping table with accurate Expedia IDs. Verify that ID was updated for the product in question. Trigger MODIFY. If this did not help, contact Expedia Engagement specialist to confirm product IDs.
Rate Plan3235OccupancyBasedPricingByLengthOfStay cannot be used for non-ARI properties.EQC AR properties only offer Occupancy Based, Per Day, Per Day with Day of Arrival or Per Day with Length of Stay pricing.Occupancy Based Pricing with Length of Stay cannot be enabled on EQC AR properties but only ARI.Contact Expedia to confirm if the property is EQC or ARi;— If the property is EQC and this is the correct setting, adjust rate to be Occupancy Based;— If the property is EQC but should be ARI, work with Expedia to change property settings.
Rate Plan3236Incompatible pricing models. Rate plan pricing model rate plans cannot be created for Property pricing model properties.On Expedia, Property Level pricing model dictates which rate level pricing models are supported. Properties set to Per Day Pricing allow rate plans with PerDayPricing, PerDayPricingByDayOfArrival or PerDayPricingByLengthOfStay model. Properties set to OccupancyBasedPricing, OccupancyBasedPricingByDayOfArrival or OccupancyBasedPricingByLengthOfStay model.(OccupancyBasedPricingByLengthOfStay is not allowed for EQC AR properties).Therefore, this error occurs when Per Day Pricing rates are being created on Occupancy Based properties or the other way around.Perform a property READ to confirm Property Level Pricing Model. If the model is incorrect, contact Expedia perform the conversion.
Rate Plan3237<bookDate> must be between 1900-01-01 and 2079-06-06.Travel Window is defined by Travel Start Date and Travel End Date. Booking Window is defined by Booking Start Date and Travel End Date.Both windows cannot start before 1900-01-01 and end after 2079-06-06.Adjust booking start or end date, depending on the date noted in Error Description, to be within the specified range.
Rate Plan3238bookDateEnd has to be on the same day or after bookDateStart.This error occurs when rate plan level Booking Window dates are out of order. Travel Window is defined by Travel Start Date and Travel End Date.Adjust booking window for the booking start date to occur before booking end date.
Rate Plan3239<travelDate> must be between 1900-01-01 and 2079-06-06.Travel Window is defined by Travel Start Date and Travel End Date. Booking Window is defined by Booking Start Date and Travel End Date.Both windows cannot start before 1900-01-01 and end after 2079-06-06.Adjust travel start or end date, depending on the date noted in Error Description, to be within the specified range.
Rate Plan3240travelDateEnd has to be on the same day or after travelDateStart.This error occurs when rate plan level Booking Window dates are out of order. Travel Window is defined by Travel Start Date and Travel End Date.Adjust travel window for the travel start date to occur before booking end date.
Rate Plan3241travelDateEnd has to be on the same day or after bookDateEnd.This error occurs when rate plan level Travel Window ends before the Booking Window. Travel Window is defined by Travel Start Date and Travel End Date.Verify Travel Window for the rate in question; Verify Booking Window for the rate in question; Adjust the end dates in order for Booking End Date to be before or on the same date as Travel End Date.
Rate Plan3242Element maxAdvBookDays has to be a number between 0 and 500.This error occurs when Advance Booking window is incorrectly set.Expedia has a limit on Advance Booking Window - the minimum accepted value is 0 days and maximum - 500 days.Adjust "Maximum Advance Booking" setting to be within the 0 - 500 days range.
Rate Plan3243minAdvBookDays cannot be greater than maxAdvBookDays."AdvBookDays" defines Advance Purchase restriction, i.e. how far into the future the rate can be booked.Minimum Advance Purchase cannot be a higher value than Maximum Advance Purchase.The lowest acceptable value is 0, the highest - 500.Adjust minimum and/or maximum Advance Purchase settings for the min. value to be lower than max. value.
Rate Plan3250Only 1 taxable and 1 non-taxable Per Stay Service Fees can be specified.On Expedia, Per Stay service fees can have both taxable and non-taxable charges. However, the same message cannot include more than one taxable and more than one non-taxable value.
Rate Plan3251amountPerNight must not be negative.This error occurs when Service Fee value for Per Night charge is set to a negative value.Service Fees should only be positive numbers.Adjust Per Night Service Fee Charge to be a positive value.
Rate Plan3252amountPerNight must not be greater than 12000000.This error occurs when Service Fee for Per Night charge exceeds maximum allowed value.Adjust Per Night Service Fee Charge to be within specified, allowed range.
Rate Plan3253amountPerStay must not be negative.This error occurs when Service Fee value for Per Stay charge is set to a negative value.Service Fees should only be positive numbers.Adjust Per Stay Service Fee Charge to be a positive value.
Rate Plan3254amountPerStay must not be greater than 12000000.This error occurs when Service Fee for Per Stay charge exceeds maximum allowed value.Adjust Per Stay Service Fee Charge to be within specified, allowed range.
Rate Plan3255percent per stay must not be negative.This error occurs when Service Fee for Per Stay charge is set to percentage and the value is negative.Per Stay Fee does not support negative values.Adjust Per Stay Service Fee Charge to be a positive value.
Rate Plan3256Percent per stay must not be greater than 1.This error occurs when Service Fee is set as percentage and the value is passed as % instead of the decimal: 50 (or 50%) instead of 0.5.Ensure that percentage value is entered.If this error is encountered, please contact your DEV/TECH support to confirm why the value was not translated correctly.
Rate Plan3258Per Person service fees 'amountPerNight' must not be negative.This error occurs when Service Fee for Per Person charge is set to the negative value. Fees do not support negative values.Adjust Per Person Fees to be a positive value.
Rate Plan3259Per Person service fees 'amountPerNight' must not be greater than 12000000.This error occurs when Service Fee for Per Person charge exceeds maximum allowed value.Adjust Per Person Service Fee Charge to be within specified, allowed range.
Rate Plan3260Per Person service fees 'amountPerStay' must not be negative.This error occurs when Service Fee for Per Person charge is set to the negative value. Fees do not support negative values.Adjust Per Person Fees to be a positive value.
Rate Plan3261Per Person service fees 'amountPerStay' must not be greater than 12000000.This error occurs when Service Fee for Per Person charge exceeds maximum allowed value.Adjust Per Person Service Fee Charge to be within specified, allowed range.
Rate Plan3262Per Person service fees must define an age category.This error occurs when at least one Per Person Service Fee is missing Age Category.Ensure that each Service Fee Per Person is set for a specific age category.
Rate Plan3263Per Person service fees must define both start and end dates.This error occurs when at least one Per Person Service Fee is missing date ranges.Ensure that each Service Fee Per Person is set for a specific date range.
Rate Plan3264Per Person service fees must define an end date that is after or equal to the start date.This error occurs when at least one Per Person Service Fee is set for out of order date range, for instance, with Start Date set to October and End Date set to September of the same year.Ensure that each Service Fee Per Person is set for a specific date range specified in chronological order.
Rate Plan3265Per Person service fees start date cannot be after or equal to 2079-06-06.This error occurs when Per Person Service Fee is used. The maximum allowed date for both Start and End date is 2079-06-06.Ensure that Per Person Service Fee start date is before 2079-06-06.
Rate Plan3729Expedia Collect partner code is already used under this room type by rate plan ID: []This error occurs when the rate plan that already exists on EPC under the specified room is being mapped anew under the same room.Perform read (GET); Verify if Expedia Rate Plan ID was saved in CRS/PMS the Mapping Table; If Expedia Rate Plan ID was saved, rate modified will be triggered instead of create;— If Expedia Rate Plan ID was not saved, reach out to Central Ops Engagement specialist at Expedia to provide you with the rate plan ID. Enter this ID in the Mapping table manually.Once ID was saved in the mapping table, modify message can be triggered.
Rate Plan3730Hotel Collect partner code is already used under this room type by rate plan ID: []This error occurs when the rate plan that already exists on EPC under the specified room is being mapped anew under the same room.Perform read (GET); Verify if Expedia Rate Plan ID was saved in CRS/PMS the Mapping Table; Verify if Expedia Rate Plan ID was saved in Channel Code in the Mapping Table;— If Expedia Rate Plan ID was saved, rate modified will be triggered instead of create;— If Expedia Rate Plan ID was not saved, reach out to Central Ops Engagement specialist at Expedia to provide you with the rate plan ID. Enter this ID in the Mapping table manually.Once ID was saved in the mapping table, modify message can be triggered.
Rate Plan3732You must have at least one active standalone rate plan before you may create/enable an active NON- standalone rate plan.This error occurs when a different rate type (Corporate, Package) is being activated before the standalone rate.Verify the rate plan type of the failed rate; If this rate should be NON-standalone, create a standalone rate first.
Rate Plan3733Standalone rate plan could not be deactivated or deleted. A room type having active Package or Corporate rate plans should have at least one active standalone rate plan.This error occurs when standalone rate is being deactivated before all other rate types (Corporate, Package) are inactivated under the same room.Verify the rate plan type of the failed rate; If this rate should be standalone rate, set other NON-Standalone rates under the indicated room to inactive first. If NON-Standalone rates should remain active:— first create new standalone rate,— then, deactivate failed standalone rate.
Rate Plan3734Package rate plan cannot have HotelCollect business model.Package Rates can only have Expedia Collect (a.k.a. Merchant) distribution (i.e. business) model.Ensure that Package Rate is not set as Expedia Traveler Preference rate (i.e. does not have Hotel Collect model).
Rate Plan3735Cannot enable Corporate or Package rate plan until the room type has at least one active Standalone rate plan.This error occurs when Corporate or Package rates are attempting to be mapped without Standalone rate being mapped first.in CRS/PMS mapping table, verify that Standalone rate for the room in question is mapped to Expedia: If there is no rate plan ID displayed in the mapping table for this rate, trigger a create; Once standalone rate plan was created on EPC for this room, trigger a create for the Corporate/Package rate that previously failed.
Rate Plan3740Cannot set flag depositRequired for ExpediaCollect distribution model.This error occurs when Create/Modify rate plan message includes "depositRequired" set to "true" for Expedia Collect rate plan. On Expedia, deposit cannot be enabled for Expedia Collect rate.If it is encountered: Verify if rate is intended to be EC only; If it is not, — Either add HC code to the rate to create Expedia Traveler Preference Rate and repush;— OR convert the rate into HC rate plan. If it is, remove deposit information.
Rate Plan3741Cannot set flag depositRequired to 'true' on a property that has no deposit policy.This error occurs when deposit policy is being enabled on the rate plan before it is created for the property.Ensure that property has Deposit Policy.If not:— Create Deposit Policy via Deposit API or EPC first.
Rate Plan3742Your property currently has active rate plans using a different pricing model than the one provided in the request. Before we can create rate plans with the provided pricing model, please either delete all existing active rate plans using the previously defined pricing model, or contact Expedia to perform a conversion.Pricing Model defined on the Property Level determines the allowed Rate Plan Level Pricing Models. This error occurs when property was converted from one model to another without deactivation of the rates. After property conversion, rates with the original Pricing Model should be deactivated and remapped.Set properties with original Pricing Model to inactive (or Delete them); Create rates with the new Pricing Model anew.or contact Expedia Engagement team to assist you with inactivation.
Rate Plan3902Cancel Policy penalties can't have the same deadlineOne penalty should be defined for the deadline 0; Multiple penalties cannot be defined for the same deadline. See error 3075 for the cancellation logic application.If this error is encountered, please contact your DEV/TECH support.
Rate Plan3903Cancel Policy penalties can't have the same deadline in exceptionsPlease see error 3902 which refers to the "default" cancellation policy settings. Error 3903 occurs for the same scenario just in the cancellation exceptions.If this error is encountered, please contact your DEV/TECH support.
Room Type3113Duplicate bedding option found.This error occurs when Bedding type is listed twice. Expedia allows more than one bedding of the same type for one room but this should be defined in quantity of bedding.Please ensure that the total sum of the beds of the same type if specified. Please contact your DEV/TECH team to ensure that the "translation" logic from the UI to the message is correct.
Room Type3114Duplicate extra bedding found.Please see error 3113. Error 3114 applies the same logic, just to "Extra Bedding".Please ensure that the total sum of the beds of the same type if specified. Please contact your DEV/TECH team to ensure that the "translation" logic from the UI to the message is correct.
Room Type3203Room type ID not found. You specified a room type ID that does not exist for this property.On Expedia: — Room Type ID is a unique value assigned to one specific Hotel. This error occurs when Expedia Room Type ID stored in CRS/PMS Mapping Table does not belong to the Expedia Hotel ID stored in CRS/PMS mapping table.FTrigger a FETCH to update CRS Mapping table with accurate Expedia IDs. Verify that ID was updated for the product in question. Trigger MODIFY. If the above did not help, contact Expedia Engagement specialist to confirm product IDs. Update product IDs in CRS/PMS mapping table manually.If this error is returned on CREATE message: Verify the room code is saved in CRS/PMS and included in the message;— If not, please add room code and retrigger the message.
Room Type3205Invalid common name for room type.
Room Type3206Room type partner code is required and must not exceed [] characters.This error occurs when create message does not contact room code.Ensure that new room has its code set in place.
Room Type3207Room Type ID is not associated to that Property ID.On Expedia: — Room Type ID is a unique value assigned to one specific Hotel. This error occurs when Expedia Room Type ID stored in CRS/PMS Mapping Table does not belong to the Expedia Hotel ID stored in CRS/PMS mapping table.FTrigger a FETCH to update CRS Mapping table with accurate Expedia IDs. Verify that ID was updated for the product in question.Trigger MODIFY.If the above did not help, contact Expedia Engagement specialist to confirm product IDs. Update product IDs in CRS/PMS mapping table manually.If this error is returned on CREATE message: Verify the room code is saved in CRS/PMS and included in the message;— If not, please add room code and retrigger the message.
Room Type3208Invalid smoking preference <smoking preference>.Smoking Preferences have only two options: Smoking and Non-Smoking. Therefore, this error occurs when smoking preference is set to a different value.Ensure that only one option is selected for the room, either smoking or non-smoking.
Room Type3210The number of adults cannot be greater than the total max occupancy.This error occurs for BTO V2 Product API format (i.e. not supporting bedrooms and living areas). Maximum Occupancy has to be equal or greater than Maximum Adults.Ensure that maximum occupancy equals or is greater than maximum adults.
Room Type3211The min age of category [] must not exceed min age of category [].This error occurs when two Age categories have overlapping ages.Ensure that each age category has its own minimum age value.
Room Type3212Age category 'null' cannot be specified more than once.
Room Type3213Age category 'Adult' must be specified.This error occurs when Child Age categories are specified without specifying Adult Age category.Ensure that Adults have minimum age value defined.
Room Type3215Missing mandatory smoking preferences.On Expedia, Smoking Preference should always be defined for each room type. Therefore, this error occurs if smoking preference element is not included in the message.Ensure that smoking preference is selected. Verify if your DEV/TECH team if default value can be included in the message if nothing is selected in the User Interface.
Room Type3217Room Type Resource ID cannot be specified in a create request, it must be empty or missing.Resource ID is Expedia Room Type ID.This ID is generated after the room is created. Therefore, this error occurs when CREATE message includes this ID, which means that (1) either CREATE is sent instead of the MODIFY or (2) ID of another room is included in the message.Verify if the intended action is CREATE or UPDATE. Verify if Expedia Room ID is stored in the system. Verify if the room already exists under the specified property.— If CREATE message was intended (room does not exist under the specified room):Please verify with your DEV/TECH team why Room ID is included in the CREATE message.— If MODIFY message was intended (room does exist under the specified room):Please verify with your DEV/TECH team why CREATE message was sent instead of MODIFY.
Room Type3218The Room type name is missing.Invalid 'name'. Must include either 'attributes' or 'value' for room name generation.This error occurs when room type name is not specified.Ensure that at least room type is populated.
Room Type3219Type of room is missing or invalid, please provide a value defined by the API specification.This error occurs when "typeOfRoom" is not included in the message or it is included but is listing unsupported value.Ensure that room type is populated for the failed room.
Room Type3220Room class is invalid, please provide a value defined by the API specification.This error occurs when "roomClass" is included in the message but is listing an unsupported value.Ensure that supported by Expedia Room Class is selected.
Room Type3221Bedroom details is missing or invalid, please provide a value defined by the API specification.This error occurs when "bedroomDetails" is included in the message but is listing an unsupported value.Ensure that the value sent is supported as documented in the bedroomDetailsEnum.
Room Type3222Featured amenity is invalid, please provide a value defined by the API specification.This error occurs when "featuredAmenity" is included in the message but is listing an unsupported value.Ensure that Featured Amenity is set to the supported by Expedia value or is not selected.
Room Type3223View is invalid, please provide a value defined by the API specification.This error occurs when "view" is included in the message but is listing an unsupported value.Ensure that View is set to the supported by Expedia value or is not selected.
Room Type3224Area is invalid, please provide a value defined by the API specification.This error occurs when "area" is included in the message but is listing an unsupported value.Ensure that area is set to the supported by Expedia value or is not selected.
Room Type3225Custom label cannot exceed 37 characters.Custom Label is a free text and cannot exceed 37 characters.Ensure that custom label does not exceed 37 characters.
Room Type3226The number of children has to be at most 1 less than the total max occupancy.This error occurs when the number of allowed children is higher than total allowed occupancy. For instance:Maximum occupancy (all people) is 6 yet maximum children number is set to 7.Access room level settings in CRS/PMS; Verify maximum allowed occupants; Adjust maximum allowed children to be at least 1 occupant less than the max. total occupancy.
Room Type3227Age category 'Adult' maximum occupants must be at least 1.This error occurs when Adult occupancy category is specified without a value or with "0".Ensure that maximum occupancy for Adults is specified.
Room Type3228When providing room size/floor size, both squareFeet and squareMeters values have to be provided.This error occurs when room/floor size is only listed in sq. meters or sq. feets, both formats should be included.Ensure that room size is either not utilized or both sq. meters and sq. feet are specified.
Room Type3229RoomSize squareMeters should be a whole number between 1 and 100000This error occurs when sq. feet identifying room size are sent with decimals.• Access room level settings in CRS/PMS; Verify room size; Adjust square feet to be a whole number.
Room Type3230A maximum of <maximum room views> views can be specified for a room type.This error occurs when more than 2 views are provided for the room.Ensure that only 2 room views are selected for the failed room.
Room Type3231Total Max Occupancy must not be lower than the number of people included in the base rate of any rate plans for this room type.
Room Type3244Age category [] is currently not defined as supported by your property. If you feel you got this error by mistake, please contact Expedia to resolve.This error is caused by the Age Category disparity between the room and its property settings.Contact Expedia Central Ops team (Engagement) to adjust Age Categories at Property Level.
Room Type3245Standard bedding must have at least 1 or at most 2 bedding options. Bedrooms and living rooms cannot define more than 2 'bedding' groups.This error occurs when there are more than 2 bedding options selected for the room.Ensure that only 2 bedding options are selected.
Room Type3246Child age category is not specified.
Room Type3257A property can have up to 99 active room types. This property has reached this limit.This error occurs when the limit of active rooms is reached.• Deactivate/Delete rates on the room types that should no longer be active.
Room Type3268Max Occupants provided in request exceeds the permissible limit of 20.
Room Type3269Room Type requires at least 1 bedroom.This error occurs only if you are using the V3 version for RoomType management. (i.e. for the configuration where bedroom and living room spaces are supported). This error occurs when bedding and occupancy are not included in the message for the new room type.Ensure that bedding and occupancy are specified at the room create.
Room Type3277Maximum Occupancy Total count cannot be less than the Adult or Children countThis error occurs only if you are using the V3 version for RoomType management (i.e. supporting bedrooms and living areas). Maximum Occupancy has to be equal or greater than Maximum Adults.Ensure that maximum occupancy equals or is greater than maximum adults.
Room Type3278Room Name cannot use 'includeBedType' when 'standardBedding' is not provided. Remove the usage of 'includeBedType' from the Room Name 'attributes' or define 'standardBedding'.This error occurs when room is created without any "Bed Type" selected in "Bed Type Assignment".Verify room level settings; Assign "Bed Type" to "Bedding Type Assignment" section.
Room Type3279maxOccupancy' is required when 'standardBedding' is not provided.This error occurs only if you are using the V2 version for RoomType management (i.e. configuration that does not support bedrooms/living room spaces) and occurs when bedding and occupancy are not included in the message for the new room type.Ensure that bedding and occupancy are specified at the room create.
Room Type3301Standard bedding is missing. Bedroom must define at least 1 'bedding' group.This error occurs when bedding is not specified.Ensure that bedding is specified.
Room Type3302Bedding is incomplete or has invalid elements. It is defined as a list of options. Each option must have a quantity greater or equals to 1, a type of bed and, optionally, a bed size.This error occurs when Bedding Information in the message is incomplete.Ensure that bedding is selected for the failed room type.Ensure that all of the required elements (count, type and size) are selected.
Room Type3303Extra bedding is incomplete or has invalid elements.It must have a quantity greater or equal to 1, a type of bed and, optionally, a bed size.This error occurs when not all required information is provided for Extra Bedding configuration.Ensure that all required information is provided for the extra bedding.
Room Type3304Invalid extra bed type for a surcharge.This error occurs when an unsupported bed type is listed with the surcharge.Ensure that surcharge is defined for Crib or Rollaway bed only.Remove surcharge for any other bed type.
Room Type3305Extra bedding type of 'Free' cannot have an amount specified.This error occurs when contradictory information is provided for the surcharge of the extra bedding.Ensure that— If extra bedding is free, there is no amount selected for the surcharge and no surcharge type;— If extra bedding requires a surcharge, its type is not set to "Free".
Room Type3306Non Free Extra bedding type must have an amount specified.This error occurs when contradictory information is provided for the surcharge of the extra bedding.Ensure that— If extra bedding is free, there is no amount selected for the surcharge and no surcharge type;— If extra bedding requires a surcharge, its type is not set to "Free".
Room Type3307Non Free Extra bedding type must have an amount greater than 0.This error occurs when contradictory information is provided for the surcharge of the extra bedding.Ensure that— If extra bedding is free, there is no amount selected for the surcharge and no surcharge type;— If extra bedding requires a surcharge, its type is not set to "Free".
Room Type3308Extra bedding type of 'Unknown' is not supported for the creation of a room type.This error occurs when charge for Extra Bedding is set to "Unknown" type (as opposed to Free, Per DayPer Night, etc.) during creation. "Unknown" cannot be set as a charge type during creation.Ensure that if Extra Bedding Type is required for this new room, surcharge type is either specified or set to free.
Room Type3309Extra bedding surcharge of type 'Unknown' is not supported. It may have been returned by the GET operation. It means the surcharge information is incomplete and must be fixed as part of this PUT.This error occurs when charge for Extra Bedding is set to "Unknown" type (as opposed to Free, Per DayPer Night, etc.) during creation. "Unknown" cannot be set as a charge type during creation.Ensure that if Extra Bedding Type is required for this new room, surcharge type is either specified or set to free.
Room Type3310Extra bedding surcharge of type 'Unknown' is not supported. It may have been returned by the GET operation. It means the surcharge information is incomplete and must be fixed as part of this PATCH, before any other update can be applied to this room type.This error occurs when charge for Extra Bedding is set to "Unknown" type (as opposed to Free, Per DayPer Night, etc.) during creation. "Unknown" cannot be set as a charge type during creation.Ensure that if Extra Bedding Type is required for this new room, surcharge type is either specified or set to free.
Room Type3400Unrecognized amenity code: []This error occurs when Room Amenities message (as opposed to Room or Rate message) contains unsupported amenities.Please contact your DEV/TECH team if this error is encountered.
Room Type3401Amenity code [null] cannot be specified more than once.This error occurs on Room Amenities Call and occurs when amenities are used twice, with different options.Ensure that only one amenity is used.Ensure that contradicting amenities are not selected.
Room Type3404Unrecognized amenity detailCode [] provided for code [].This error occurs when Room Amenities message (as opposed to Room or Rate message) contains unsupported amenities.Please contact your DEV/TECH team if this error is encountered.
Room Type3405Missing required value for amenity code [].This error occurs on Room Amenities Call and occurs when amenities are listed without the value.Ensure that correct amenity (i.e. amenity mapped to Expedia) is selected.If correct amenity is used, please verify with your TECH/DEV team why the amenity option (value) is not being passed correctly.
Room Type3406A value was provided for amenity code [] but this amenity doesn’t support value.This error occurs on Room Amenities Call and occurs when amenities that do not offer value selection are listed with the value.Ensure that correct amenity (i.e. amenity mapped to Expedia) is selected.Ensure that its selected value matches Expedia specifications.If correct amenity is used, please verify with your TECH/DEV team why the amenity option (value) is not being passed correctly.
Room Type3407Invalid value received for amenity code []. Value needs to be between [0.5] and [20.0].This error occurs when numerical value of the specified amenity is outside of the allowed range.Ensure that value for the amenity specified in the Error Description has values within the allowed range.
Room Type3408Invalid value received for amenity code []. Value needs to be in increments of [].This error occurs when amenities values do not match defined by Expedia limits (For instance, when Bathroom count exceeds 20).Ensure that correct amenity (i.e. amenity mapped to Expedia) is selected.Ensure that its selected value matches Expedia specifications.If correct amenity is used, please verify with your TECH/DEV team why the amenity option (value) is not being passed correctly.
Room Type3731Room type partner code is already used under this property by room type ID: []This error occurs when a room already under the hotel is being mapped anew under the same hotel. At Expedia, room type code can only be used under the hotel once.Perform read (GET); Verify if Expedia Rate Plan ID was saved in CRS/PMS the Mapping Table; Verify if Expedia Room ID was saved in Channel Code in the Mapping Table;— If Expedia Room ID was saved, room modified will be triggered instead of create;— If Expedia Room ID was not saved, reach out to Central Ops Engagement specialist at Expedia to provide you with the room ID. Enter this ID in the Mapping table manually.Once ID was saved in the mapping table, modify message can be triggered.

Success responses:

Status Code

Description

Response Model

200

successful operation

HTML Page

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

Status Code

Meaning

Retry

200

Success for read and update operations

No subsequent action needed

201

Success for create operations

No subsequent action needed

204

Success for delete operations

No subsequent action needed

400

Errors due to incorrect user input

Fix input and retry

401

Authentication error

Verify username or password and retry

403

Authorization error

Verify the property is connected to your system and retry

404

Invalid resource

Verify resourceID and retry

405

Invalid/unsupported method on resource

Verify method and retry

406

Unsupported media type for response (only application/vnd.expedia.eps.product-v2+json is supported)

Verify media type in “Accept” header and retry

409

Conflicting data

Verify partnerCode and retry

415

Unsupported media type for requests (only application/vnd.expedia.eps.product-v2+json is supported)

Verify media type in “Content-Type” header and retry

500

Internal system error (should not be retried)

Contact Expedia Support. Do not retry

503

Temporary internal system error (should be retried)

Retry

504

Timeout error (should be retried)

Retry