ReferenceProperty API

Error handling

Error messaging in Property API helps the partner understand why a read (GET), create (PUT), update (PUT), or deactivation (DELETE) request is denied.

Expedia Group recommends a robust retry strategy when resolving errors.

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, the partner 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 the partner's 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.

HTTP status codes

After submitting a request for any of the endpoints, acknowledgement or errors will be returned in the HTTP headers. 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.

Status Code

Meaning

Retry

Notes

2xx

Success message

No subsequent action needed

202

Request successfully received and is processing

No subsequent action required.

To get processing status, see the status attribute contained in the response body.

4xx

Error message

No

400

Validation error

Fix input and retry

Must address errors listed in the Validation attribute contained within the response body and resubmit.

5xx

Internal error

Yes

Internal system error when attempting to process the message.

Property status codes

The reasonCodes field represents all the reasons the property has a particular status.

Status code

Reason codes

Description

Action required

ExpediaIdAssigned

None

FinanceSetupPending

None

OnboardingFailed

DeclinedOnReview

EpcOnboardingInProgress

InternalError

InvalidCoordinates

InvalidCountryCode

InvalidProperty

InvalidPropertyName

MissingBillingCurrencyCode

MissingContactInfo

MissingExpediaId

NoValidAddresses

NoValidPhoneNumbers

OfacCheckFailed

PropertyDisabled

PropertySuspended

UnsupportedLocation

OnboardingSucceeded

None

PendingReview

BookableProvidersExist

BusinessModelChanging

ContractTermsChanging

CurrencyCodeChanging

RateAcquisitionTypeChanging

PropertySaved

None

VendorIdAssigned

None

Property status error codes

Public CodeReason CodeMessages
OnboardingFailedInvalidPropertyNameProperty name must be more than 3 characters. Submitted value: <example>
OnboardingFailedInvalidCoordinatesLatitude/longitude cannot be 0/0 OR an invalid range. Submitted values are:<example>
OnboardingFailedNoValidAddressesNo valid addresses found (line1, city, and country code required)
OnboardingFailedNoValidPhoneNumbersAt least 1 phone number is invalid for contacts, value cannot be NULL. Submitted value:<example>
OnboardingFailedInvalidEmailAddressAt least 1 email address is invalid for contacts, value cannot be NULL or contain multiple \"@\". Submitted value:<example>
OnboardingFailedMissingContactInfoValues for 'First' and 'Last' Names must be at least 2 characters. Submitted values:<example>
OnboardingFailedNoContentImagesContent image urls are not specified as absolute addresses (e.g. http://example.com/image/123.jpg).
OnboardingFailedCurrencyCodeMismatchFor Expedia Collect or Expedia Traveler Preference properties, the CurrencyCode and BillingCurrencyCode must match.
OnboardingFailedMissingContactInfoRequired contact information is missing. ReservationManager must be present with a valid email address.
OnboardingFailedMissingBillingCurrencyCodeBilling currency code is required
OnboardingFailedUnsupportedLocationUnsupported location. Please contact your account manager for more details.
OnboardingFailedInvalidPropertyFinance profile with the appropriate country and currency cannot be found, please confirm this is set up properly.
OnboardingFailedInvalidPropertyPostal code is missing from this property. Please provide postal code to continue onboarding.
OnboardingFailedInvalidPropertyState cannot be null for this property. Please provide a State to continue onboarding.
OnboardingFailedInvalidPropertyThe currency supplied in the finance profile does not match the currency set on the property.
OnboardingFailedInvalidPropertyInvalid characters have been entered for State. Please refer to the accepted characters list.
OnboardingFailedInvalidPropertyFinance profile is not configured. Please work with Expedia support to address this.
OnboardingFailedInvalidPropertyAddress or Postal code is configured with characters that are not accepted. Please refer to the list of accepted characters.
OnboardingFailedInvalidPropertyThis currency is not supported for the finance profile configured. Please work with Expedia support to address this.
OnboardingFailedInvalidPropertyFinance profile with the appropriate country cannot be found, please confirm this is set up properly.
OnboardingFailedInvalidPropertyFinance profile with the appropriate country and currency cannot be found, please confirm this is set up properly.
OnboardingFailedInvalidPropertyCurrency supplied at property level does not match the currency set on the finance profile.
OnboardingFailedMissingRequiredContactType[Reservation Manager, Alternate Reservation Manager] contact types are required. Please, provide a [Alternate Reservation Manager] contact type.
OnboardingFailedMissingRequiredContactTypeCould not map any CONTACT fields for property <example> since it has no Contacts!
OnboardingFailedLatLongNotMatchedLat/Long (<example>,<example>) do not match with the country code (<example>) sent in the request. Please ensure that the lat/long sent matches the country code sent.
OnboardingFailedDuplicatedProperty <example> from <example> is marked as duplicate because you have provided another property <example> which appears to be the same with EID: <example>. If you think this is an error, please contact your Technical Relationship Manager.
ContentValidationFailedInvalidPropertyNameHotel Name is too long and we support up to 255 characters
OnboardingFailedMissingRequiredInfoMissing mandatory information addressLine1. The value (<example>) is either null or less than (5) characters! Cannot provide shell creation information
OnboardingFailedNoValidAddressesADDRESS_COUNTRY_CODE mapping failed, COUNTRY_CODE is missing in RFD
OnboardingFailedMissingRequiredInfoOnboarding failed. Please provide at least 3 images to onboard this property.
OnboardingFailedMissingRequiredInfoOnboarding failed, structure type must be present. Please provide a structure type.
OnboardingFailedMissingRequiredInfoNumber of bedrooms and Number of bathrooms are mandatory info. Please provide them.
PropertyOnboardValidationFailedInvalidPropertyProperty is marked as not valid: HomeAwayBookable Property Id: <example>, Expedia Property Id: <example>.
OnboardingFailedInvalidPropertySettingsDistribution models must be specified
404Property not found: ExpediaId <example>
1014Property <example> has already been submitted as expedia Id: <example>.

Warning codes

Warning Code

Message

Recommendation

4011

The following attributes [XX] are not configured to be mapped

The entered attributes are not supported by Expedia. Please refer the documentation and send the correct data.

4013

The value XX entered for the attribute X is not in the permissible list. Could you please review documentation for permissible values and fix any issues ?

The value entered is not supported by Expedia. Please refer the documentation and send the correct data.

4014

XX is in conflict with these attributes XX. Could you please review them and fix any issues ?

This warning occurs when there are conflicting attributes sent. For example: SMOKING_POLICY|DESIGNATED_SMOKING_AREA and SMOKING_POLICY|SMOKE_FREE_PROPERTY for a same property is confliction. Please refer to the documentation and send only the valid ones.