/ctrip/attractions/search

POST /api/ctrip/attractions/search

Price: 20 credits

List Ctrip attractions in a destination, ordered by Ctrip's recommended order by default (sort recommended) or by rating, popularity or ticket sales when requested: name, area, rating and review count, ticket price and list price in CNY, opening status, ranking badge, tags, coordinates and cover image.

How to use it

Use to rank what to see in a destination. Returns up to 300 attractions. Pass id and city_alias into ctrip/attractions for opening hours, policies and reviews.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• city_alias string required — Ctrip destination alias as used in you.ctrip.com URLs (examples: "shanghai2"; maxLength: 60; pattern: ^[A-Za-z]+\d+$)
• count integer required — Max number of attractions to return (min: 1; max: 300)
• sort string — Result order: Ctrip's recommended order, top-rated (rating and review count combined), popularity or ticket sales (default: "recommended"; one of: "recommended", "rating", "popularity", "sales")

Response

• @type string (default: "CtripAttractionCard")
• id string required
• poi_id string nullable
• name string nullable
• zone_name string nullable
• city_id integer nullable
• city_name string nullable
• rating number nullable
• review_count integer nullable
• price number nullable
• market_price number nullable
• price_type string nullable
• currency string nullable
• is_free boolean nullable
• open_status string nullable
• ranking string nullable
• heat_score number nullable
• tags array (default: [])
• features array (default: [])
• distance string nullable
• latitude number nullable
• longitude number nullable
• is_advertisement boolean nullable
• image string nullable
• 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 destination exists for this alias 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.