/trip/hotels/search

POST /api/trip/hotels/search

Price: 10 credits

Search Trip.com hotels in a city by numeric city id for given check-in/check-out dates. Returns the city's top hotels with id, name, star rating, category, guest review score with category subscores and review count, the lowest nightly from-price, location (address, district, city/province/country, coordinates), a review snippet and photos.

How to use it

Search hotels in a Trip.com city by numeric city_id (resolve a city name to its id via trip/destinations/search). Optionally pass check_in/check_out dates for the from-price. Returns items with id, name, star, category, score, score_description, review_count, score_details, price, currency, city_id, city_name, province_id, country_id, address, position_desc, zone_names, latitude, longitude, review_snippet, image, images and url.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• city_id integer required — Trip.com numeric city id to search hotels in (examples: 633; min: 1)
• check_in string nullable — Check-in date (YYYY-MM-DD); defaults to a near-future date (format: date)
• check_out string nullable — Check-out date (YYYY-MM-DD); defaults to the day after check-in (format: date)
• count integer required — Max number of hotels to return (min: 1)

Response

• @type string (default: "TripSearchHotel")
• id string required
• name string nullable
• star integer nullable
• category string nullable
• score number nullable
• score_description string nullable
• review_count integer nullable
• score_details array (default: [])
  • @type string (default: "TripSearchScoreDetail")
  • name string required
  • score number nullable
• price number nullable
• currency string nullable
• city_id integer nullable
• city_name string nullable
• province_id integer nullable
• country_id integer nullable
• address string nullable
• position_desc string nullable
• zone_names array (default: [])
• latitude number nullable
• longitude number nullable
• review_snippet string nullable
• image string nullable
• images array (default: [])
• url string nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — No hotels found for the given city id Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.