Retrieve Expedia Rapid hotel property content (descriptions, amenities, photos) separately from availability/pricing, and keep a local content cache in sync.

Steps

1. Authenticate with your Rapid API key/shared secret and call the Property Content API at https://test.ean.com/v3/properties/content (prod: api.ean.com), passing language, supply_source, and include filters to scope which content fields come back.
2. For bulk bootstrapping instead of per-ID lookups, pull the Property Catalog File and/or Property Content File download-link endpoints, but prefer the Property Content API if you rely on expanded global inventory since the File APIs have limited support there.
3. Resolve numeric/coded fields in the response (amenities, categories, chains, etc.) against the separate Content Reference Lists endpoints, noting reference lists are English-only even when your content response is localized.
4. Set up incremental sync using date_added_start, date_added_end, date_updated_start, and date_updated_end query params so you only re-pull properties that changed instead of the full catalog.
5. Periodically call GET https://test.ean.com/v3/properties/inactive?since=<date> to get a list of property_ids that went inactive, and purge them from your content store.
6. Keep this content store entirely separate from live pricing: join to the Shopping API by property_id only at query time, never persist rates from the Content API.