--departure-city <code> | No | departure city code, ISO-country + city, e.g. GBLON for London. JSON: departure_city. | |
--arrival-city <code> | No | arrival city code, ISO-country + city, e.g. FRPAR for Paris. JSON: arrival_city. | |
--departure-stations <codes...> | No | specific departure station codes, e.g. GBLONLPB. More specific than —departure-city, and wins when both are given. JSON: departure_stations. | |
--arrival-stations <codes...> | No | specific arrival station codes. Wins over —arrival-city. JSON: arrival_stations. | |
--date <date> | Yes | departure date (YYYY-MM-DD). JSON: departure_date. | |
--return-date <date> | No | return date (YYYY-MM-DD), makes it a round trip. JSON: return_date. | |
--adults <n> | No | number of adults (default 1). JSON: passengers[].pax. | "1" |
--children <ages...> | No | children ages, e.g. 8 12, each becomes its own passenger group. JSON: passengers[].max_age. | |
--carriers <codes...> | No | restrict to specific carrier codes, e.g. HEXR. JSON: carrier_codes. | |
--currency <code> | No | ISO 4217 currency code, e.g. GBP. JSON: currency. NOTE: currently REQUIRED in practice, the provider rejects a search without one, and the schema marking it optional is a known server-side bug. | |
--locale <locale> | No | response locale, e.g. en. JSON: locale. | |
--user-intent <text> | No | the end user’s request in their own words, forwarded to Jinko for observability and relevance (avoid PII). Env fallback: JINKO_USER_INTENT. JSON: intent.user_intent. | |
