/ctrip/attractions

POST /api/ctrip/attractions

Price: 20 credits

Get a Ctrip attraction by id: name, rating with category scores and review count, address, ranking, introduction, opening status and hours, recommended visit length, current notice, visitor policies, facilities, review tags, the first page of reviews, visitor questions, nearby attractions, video and photos.

How to use it

Use to plan a visit: opening hours, ticket and age policies, and what recent visitors say. Both id and city_alias come from ctrip/attractions/search.

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+$)
• id string required — Ctrip attraction id (examples: "1412255"; maxLength: 20; pattern: ^\d+$)

Response

• @type string (default: "CtripAttraction")
• id string required
• poi_id string nullable
• name string nullable
• name_en string nullable
• city_id integer nullable
• city_name string nullable
• city_name_en string nullable
• rating number nullable
• review_count integer nullable
• address string nullable
• ranking string nullable
• heat_score number nullable
• introduction string nullable
• open_status string nullable
• opening_hours string nullable
• today_hours string nullable
• recommended_duration string nullable
• notice_title string nullable
• notice_text string nullable
• policies array (default: [])
  • @type string (default: "CtripAttractionNamedText")
  • name string required
  • text string nullable
• facilities array (default: [])
  • @type string (default: "CtripAttractionNamedText")
  • name string required
  • text string nullable
• rating_details array (default: [])
  • @type string (default: "CtripAttractionScore")
  • name string required
  • score number nullable
• review_tags array (default: [])
  • @type string (default: "CtripAttractionReviewTag")
  • name string required
  • review_count integer nullable
• reviews array (default: [])
  • @type string (default: "CtripAttractionReview")
  • id string required
  • text string nullable
  • rating number nullable
  • scores array (default: [])
    • @type string (default: "CtripAttractionScore")
    • name string required
    • score number nullable
  • author_name string nullable
  • author_image string nullable
  • traveller_type string nullable
  • ip_location string nullable
  • like_count integer nullable
  • reply_count integer nullable
  • published_at integer nullable
  • images array (default: [])
• questions array (default: [])
  • @type string (default: "CtripAttractionQuestion")
  • reply_count integer nullable
  • url string nullable
• nearby_attractions array (default: [])
  • @type string (default: "CtripAttractionNearby")
  • poi_id string nullable
  • name string required
  • rating number nullable
  • review_count integer nullable
  • distance string nullable
  • image string 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 attraction 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.