/yatra/flights/search

POST /api/yatra/flights/search

Price: 20 credits

Search Yatra one-way domestic India flights for a date: every fare option with airline, flight numbers, times, duration, stops, segments with terminals and aircraft, per-adult total and base fare with the child and infant fares of the requested passengers, promo, baggage, meal, change and cancellation rules

How to use it

Each fare option of a flight is its own result; the same flight_numbers and departure_at mark one flight.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• origin string required — Origin airport IATA code (examples: "BLR"; pattern: ^[A-Za-z]{3}$)
• destination string required — Destination airport IATA code (examples: "DEL"; pattern: ^[A-Za-z]{3}$)
• date integer required — Departure date, unix seconds (examples: 1794421800; min: 0)
• adults integer — Adult passengers (default: 1; min: 1; max: 9)
• children integer — Child passengers (default: 0; min: 0; max: 8)
• infants integer — Infant passengers (default: 0; min: 0; max: 4)
• cabin string — Cabin class (default: "economy"; one of: "economy", "business")
• count integer required — Max number of results (min: 1)

Response

• @type string (default: "YatraFlight")
• id string required
• fare_name string nullable
• fare_tag string nullable
• supplier string nullable
• airline_code string nullable
• airline string nullable
• flight_numbers array (default: [])
• origin string nullable
• destination string nullable
• departure_at integer nullable
• arrival_at integer nullable
• duration_minutes integer nullable
• stops integer nullable
• cabin string nullable
• currency string (default: "INR")
• total_fare number nullable
• base_fare number nullable
• child_total_fare number nullable
• child_base_fare number nullable
• infant_total_fare number nullable
• infant_base_fare number nullable
• fuel_surcharge number nullable
• promo_code string nullable
• promo_description string nullable
• promo_discount number nullable
• checked_baggage string nullable
• cabin_baggage string nullable
• seat_selection string nullable
• date_change_policy string nullable
• cancellation_policy string nullable
• meal string nullable
• co2_kg number nullable
• segments array (default: [])
  • @type string (default: "YatraFlightSegment")
  • airline_code string nullable
  • airline string nullable
  • flight_number string nullable
  • origin string nullable
  • destination string nullable
  • departure_at integer nullable
  • arrival_at integer nullable
  • duration_minutes integer nullable
  • departure_terminal string nullable
  • arrival_terminal string nullable
  • aircraft string nullable
  • cabin string nullable
  • meal string nullable
  • baggage string nullable
  • layover 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.