/ctrip/hotels

POST /api/ctrip/hotels

Price: 20 credits

Get a Ctrip hotel by id: name, star rating, guest score with category scores and review count, featured reviews, description, highlights, phone and email, address and coordinates, check-in and check-out times, amenities, policies, nearby landmarks and places, reservation tips, video and photos.

How to use it

Use to profile a hotel in mainland China before recommending it. Ids come from ctrip/hotels/search. Room rates are not part of the response.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• id string required — Ctrip hotel id (examples: "6238773"; maxLength: 20; pattern: ^\d+$)

Response

• @type string (default: "CtripHotel")
• id string required
• name string nullable
• name_en string nullable
• star integer nullable
• star_type string nullable
• score number nullable
• score_max number nullable
• score_description string nullable
• review_count integer nullable
• location_score number nullable
• score_details array (default: [])
  • @type string (default: "CtripHotelScoreDetail")
  • name string required
  • score number nullable
• featured_reviews array (default: [])
  • @type string (default: "CtripHotelFeaturedReview")
  • text string required
  • author_name string nullable
• description string nullable
• labels array (default: [])
• highlights array (default: [])
  • @type string (default: "CtripHotelHighlight")
  • description string nullable
• phone string nullable
• email string nullable
• address string nullable
• latitude number nullable
• longitude number nullable
• coordinate_system string nullable
• city_id integer nullable
• city_name string nullable
• province_id integer nullable
• country_id integer nullable
• check_in_time string nullable
• check_out_time string nullable
• popular_amenities array (default: [])
• amenity_groups array (default: [])
  • @type string (default: "CtripHotelAmenityGroup")
  • name string required
  • amenities array (default: [])
• policies array (default: [])
  • @type string (default: "CtripHotelPolicy")
  • lines array (default: [])
• landmarks array (default: [])
  • @type string (default: "CtripHotelLandmark")
  • landmark_type string nullable
  • description string required
  • distance string nullable
• reservation_tips array (default: [])
  • @type string (default: "CtripHotelReservationTip")
  • text string required
• nearby_places array (default: [])
  • @type string (default: "CtripHotelNearbyPlace")
  • category string nullable
  • name string required
  • distance_text string nullable
  • tags array (default: [])
  • latitude number nullable
  • longitude number nullable
• video_url 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 Ctrip hotel exists for this 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.