/trip/hotels

POST /api/trip/hotels

Price: 10 credits

Get full Trip.com hotel details by hotel id (or hotel URL): name, star rating, guest review score with category subscores and review count, full address, district, coordinates, city/province/country, hotel chain, year opened and renovated, description, contact phone and email, check-in/check-out times, property highlights, grouped amenities, nearby places, policies (child, breakfast, deposit, pet, age), reservation tips, and photos.

How to use it

Fetch a single Trip.com hotel by numeric hotel id or a hotel URL containing it. Returns one item with id, name, star, score, score_description, review_count, score_details (category scores), description, address, zone_name, latitude, longitude, city_id, city_name, province_id, province_name, country_id, country_name, chain, opened_year, renovated_year, phone, email, check_in_time, check_out_time, highlights, traffic_desc, amenity_groups, nearby_places, policies, reservation_tips, image and images.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• hotel string required — Trip.com hotel id or a hotel URL containing it (examples: "1480287", "https://us.trip.com/hotels/new-york-hotel-detail-1480287/the-plaza/"; minLength: 1)

Response

• @type string (default: "TripHotel")
• id string required
• name string nullable
• star integer nullable
• score number nullable
• score_description string nullable
• review_count integer nullable
• score_details array (default: [])
  • @type string (default: "TripScoreDetail")
  • name string required
  • score number nullable
• description string nullable
• address string nullable
• zone_name string nullable
• latitude number nullable
• longitude number nullable
• city_id integer nullable
• city_name string nullable
• province_id integer nullable
• province_name string nullable
• country_id integer nullable
• country_name string nullable
• chain string nullable
• opened_year string nullable
• renovated_year string nullable
• phone string nullable
• email string nullable
• check_in_time string nullable
• check_out_time string nullable
• highlights array (default: [])
• traffic_desc string nullable
• amenity_groups array (default: [])
  • @type string (default: "TripAmenityGroup")
  • name string required
  • amenities array (default: [])
• nearby_places array (default: [])
  • @type string (default: "TripNearbyPlace")
  • name string required
  • type string nullable
  • distance string nullable
  • description string nullable
• policies array (default: [])
  • @type string (default: "TripPolicy")
  • items array (default: [])
• reservation_tips array (default: [])
  • @type string (default: "TripReservationTip")
  • content string required
• 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 — Hotel not found (well-formed but nonexistent hotel 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.