Ctrip APIhotels.ctrip.com ↗
Access Ctrip (携程酒店) hotel data via 7 endpoints: search by city or keyword, retrieve room types, pricing, policies, and paginated guest reviews.
What is the Ctrip API?
The Ctrip Hotels API provides 7 endpoints covering hotel search, property details, room availability, and guest reviews from China's Ctrip platform (携程酒店). Use search_hotels to query listings by city ID and date range, or get_hotel_detail to pull policies, facilities, nearby POIs, and reservation tips for a specific property. City IDs are resolved via get_city_list, which returns Chinese domestic cities ready to plug into other endpoints.
curl -X GET 'https://api.parse.bot/scraper/b25cb0e8-6958-4837-9980-1645cec5a4ce/get_city_list?keyword=%E6%B9%98%E8%A5%BF' \ -H 'X-API-Key: $PARSE_API_KEY'
Returns Chinese domestic destinations usable as city_id in search_hotels and the other endpoints. Without keyword it returns the site's full alphabetical inland city list (about 2,400 entries: hot cities first, then A–Z) in one round trip; that list contains prefecture capitals (e.g. 香格里拉) but omits some prefecture-level destinations such as 迪庆藏族自治州. Supplying keyword instead queries the site's destination suggest for that name and returns only the city-type matches (typically 0–3 entries, e.g. 迪庆 with its own cityId whose hotel search covers the whole prefecture); an empty cities array means the site suggested no city for that name. Each entry carries cityName, cityId, provinceId, countryName and provinceName; provinceId is 0 in list mode and null in keyword mode, provinceName is null when the site reports none (municipalities).
| Param | Type | Description |
|---|---|---|
| keyword | string | Destination name (full or partial, Chinese) to look up, e.g. a prefecture such as 迪庆藏族自治州. When omitted the full alphabetical city list is returned. |
{
"type": "object",
"fields": {
"cities": "array of city objects with cityName, cityId (integer, use as city_id), provinceId, countryName, provinceName"
},
"sample": {
"data": {
"cities": [
{
"cityId": 1,
"cityName": "北京",
"provinceId": 0,
"countryName": "中国"
},
{
"cityId": 2,
"cityName": "上海",
"provinceId": 0,
"countryName": "中国"
}
]
},
"status": "success"
}
}About the Ctrip API
Hotel Search and Discovery
The get_city_list endpoint returns an array of Chinese domestic cities, each with cityName, cityId, provinceId, and countryName. These IDs feed directly into search_hotels, which accepts a city_id, checkin/checkout dates in either YYYYMMDD or YYYY-MM-DD format, and pagination controls (page_index, page_size). The response includes a hotelList array with per-property pricing and room details, plus hotelListAddtionInfo for pagination metadata. For name- or landmark-based lookups, search_hotels_by_keyword accepts a free-text keyword and returns mainKeywordList with matched hotels and locations within the target city.
Property Details and Room Inventory
get_hotel_detail returns a data object covering hotelPolicy, hotelReservationTips, hotelFacility, hotelPoiInfo, guest comment summaries, and hotelIntroduction for a given hotel_id. Dates are optional but affect policy and availability context. get_hotel_rooms goes deeper into inventory: it returns physicRoomMap (physical room configurations), saleRoomMap (purchasable room options with prices), roomFilterInfo, calendarInfo, and extraInfo. This endpoint is useful for building date-specific availability checks or rate-comparison tools.
Reviews and Ratings
get_hotel_reviews returns paginated reviews via commentList inside groupList, alongside commentTagList, travelTypeList, commentRating, and totalCount. Both page_index and page_size are supported. get_review_summary covers similar ground — commentTagList, commentRating, travelTypeList, filterDateList, totalCount — and additionally includes aiSummaryEntities, which provides AI-generated highlight tags not present in the paginated review endpoint. Together these two endpoints give both high-level sentiment signals and raw review text.
The Ctrip API is a managed, monitored endpoint for hotels.ctrip.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when hotels.ctrip.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official hotels.ctrip.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Build a hotel price-comparison tool for Chinese cities using
search_hotelswith date and city parameters - Aggregate guest review sentiment across hotel categories by pulling
commentTagListandcommentRatingfromget_review_summary - Populate a travel app with property amenities, policies, and nearby POI data via
get_hotel_detail - Display room type breakdowns and per-night pricing using
physicRoomMapandsaleRoomMapfromget_hotel_rooms - Enable landmark-based hotel discovery by passing location names to
search_hotels_by_keyword - Track review volume trends over time using
totalCountandfilterDateListfromget_review_summary - Resolve city names to Ctrip city IDs programmatically using
get_city_listbefore running batch hotel searches
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Ctrip offer an official developer API?+
What does `get_hotel_rooms` return beyond just prices?+
get_hotel_rooms returns physicRoomMap describing the physical room configurations (bed type, size, floor, etc.), saleRoomMap for purchasable options with rates, roomFilterInfo for available filter dimensions, calendarInfo for date-specific pricing context, and extraInfo for supplementary metadata. All fields are date-sensitive — pass checkin and checkout to get accurate availability and pricing.Does the API cover international hotels outside China?+
get_city_list returns Chinese domestic cities and their IDs; the search and detail endpoints are scoped to those cities. International Ctrip hotel listings are not covered. You can fork this API on Parse and revise it to add an endpoint targeting Ctrip's international hotel coverage.What is the difference between `get_hotel_reviews` and `get_review_summary`?+
get_hotel_reviews is paginated and returns individual review comments inside commentList, making it suitable for reading full review text in batches. get_review_summary does not paginate reviews but adds aiSummaryEntities (AI-generated highlight tags) and filterDateList, which are absent from the paginated endpoint. Use both together if you need both raw reviews and summary-level signals.Can I filter hotel search results by star rating, price range, or amenities?+
search_hotels endpoint accepts city_id, date range, and pagination parameters but does not expose filter parameters for star rating, price band, or facilities in its current form. get_hotel_rooms returns roomFilterInfo at the property level. You can fork this API on Parse and revise it to add filter parameters to the search endpoint.