/ctrip/flights/calendar

POST /api/ctrip/flights/calendar

Price: 5 credits

Lowest one-way adult fare per departure day between two cities from Ctrip's fare calendar: fare and total with taxes and fees in CNY.

How to use it

Use to find the cheapest day to fly between two cities, passed as IATA city codes such as SHA or BJS. A day without a fare comes back with no price. Days before start_date are dropped; a start_date past the source's own window returns no rows.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• departure_city_code string required — Departure city IATA code (examples: "SHA"; pattern: ^[A-Za-z]{3}$)
• arrival_city_code string required — Arrival city IATA code (examples: "BJS"; pattern: ^[A-Za-z]{3}$)
• start_date string nullable — First departure date of interest; defaults to today (format: date)
• count integer required — Max number of calendar days to return (min: 1)

Response

• @type string (default: "CtripFlightCalendarDay")
• id string required
• date string required
• departure_city_code string nullable
• arrival_city_code string nullable
• price number nullable
• total_price number nullable
• currency string nullable
• flight_number string nullable
• airline 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 — The entity was not found, or a precondition failed 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.