/qunar/flights/calendar

POST /api/qunar/flights/calendar

Price: 5 credits

Lowest one-way economy fare per departure day on a route from Qunar's fare calendar, starting today: fare in CNY, direct-flight fare, and the flight numbers behind the fare.

How to use it

Use to find the cheapest day to fly between two cities, domestic or international. Cities are passed as Chinese names. A day without a fare comes back with no price; an unrecognised city also returns days without a price, so the two cannot be told apart.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• departure_city string required — Departure city name in Chinese (examples: "上海"; minLength: 1; maxLength: 20)
• arrival_city string required — Arrival city name in Chinese (examples: "北京"; minLength: 1; maxLength: 20)
• count integer required — Max number of calendar days to return, starting today (min: 1; max: 365)

Response

• @type string (default: "QunarFlightCalendarDay")
• id string required
• date string required
• departure_city string nullable
• arrival_city string nullable
• price number nullable
• price_label string nullable
• direct_price number nullable
• direct_price_label string nullable
• original_price number nullable
• flight_numbers array (default: [])
• source string nullable
• is_disabled boolean 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 — Qunar's fare calendar answered with a non-success status for this city pair 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.