/qunar/daytrips

POST /api/qunar/daytrips

Price: 5 credits

Get a Qunar day trip by id and product id: name, departure city, tags, highlights, from-price in CNY, number sold, rating and review count, the timed itinerary with stops and coordinates, usage notes, fee notes and photos.

How to use it

Use to read what a Qunar day trip includes before recommending it: the stop-by-stop itinerary, what the fee covers and the refund terms. Both ids come from qunar/daytrips/search.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• id string required — Qunar day-trip id (examples: "3294446"; minLength: 1; maxLength: 20; pattern: ^\d+$)
• product_id string required — Qunar day-trip product id (examples: "2514337700"; minLength: 1; maxLength: 20; pattern: ^\d+$)

Response

• @type string (default: "QunarDaytrip")
• id string required
• product_id string required
• name string nullable
• departure_city string nullable
• tags array (default: [])
• highlights string nullable
• price number nullable
• currency string nullable
• sold_count integer nullable
• rating number nullable
• review_count integer nullable
• route_type string nullable
• itinerary array (default: [])
  • @type string (default: "QunarDaytripDay")
  • start_time string nullable
  • stops array (default: [])
    • @type string (default: "QunarDaytripStop")
    • time string nullable
    • name string nullable
    • description string nullable
    • stop_type string nullable
    • sight_id integer nullable
    • latitude number nullable
    • longitude number nullable
• usage_notes string nullable
• fee_notes 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 day trip 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.