/ctrip/journals/search

POST /api/ctrip/journals/search

Price: 20 credits

List Ctrip travel journals written about a destination: title, snippet, author, publish and last reply dates, trip tags, view, like and reply counts, and cover image.

How to use it

Use to find first-hand trip reports about a destination. Pass id and city_alias into ctrip/journals for the full text.

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 travel journals to return (min: 1; max: 300)
• sort string — Result order: Ctrip's popular tab or the newest journals first (default: "popular"; one of: "popular", "newest")

Response

• @type string (default: "CtripJournalCard")
• id string required
• city_alias string nullable
• snippet string nullable
• author_name string nullable
• published_date string nullable
• last_reply_date string nullable
• label string nullable
• tags array (default: [])
• view_count integer nullable
• like_count integer nullable
• reply_count integer 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.