jinko find-destination - Jinko Platform

Prices in this command’s output are integers in minor units. Money objects carry decimal_places — divide by 10 ** decimal_places to display ({ "value": 15977, "decimal_places": 2 } is 159.77, not 15,977). See Money & prices.

Discover destinations from your departure airports using cached fares for one adult, even when passenger counts are supplied. Use the results to choose a route, then run flight-search with the full passenger counts to confirm live prices and availability before quoting or booking.

Usage

jinko find-destination [options]

Options

Flag	Required	Description	Default
`--origins <codes...>`	Yes	IATA airport or city codes (e.g. JFK LGA). JSON: `origins[]`.
`--destinations <codes...>`	No	IATA airport or city codes to filter to. Omit for global discovery. JSON: `destinations[]`.
`--origin-type <type>`	No	How to interpret —origins: `city` or `airport`. Omitted: a code that names a multi-airport city is searched as the city, every other code as the airport, NYC, LON, PAR are cities; JFK, LHR, CDG are airports; LAX, MIA, LAS (a city sharing its code with its main airport) are the CITY. Send airport when the user named the airport. JSON: `origin_type`.
`--destination-type <type>`	No	How to interpret —destinations: `city` or `airport`. Omitted: a code that names a multi-airport city is searched as the city, every other code as the airport, NYC, LON, PAR are cities; JFK, LHR, CDG are airports; LAX, MIA, LAS (a city sharing its code with its main airport) are the CITY. Send airport when the user named the airport. JSON: `destination_type`.
`--departure-dates <dates...>`	No	Exact departure dates (YYYY-MM-DD), OR logic. JSON: `departure_dates[]`.
`--departure-date-ranges <ranges...>`	No	Flexible departure ranges, repeatable. Format: `YYYY-MM-DD:YYYY-MM-DD`. JSON: `departure_date_ranges[]`.
`--return-dates <dates...>`	No	Exact return dates (YYYY-MM-DD), roundtrip only. JSON: `return_dates[]`.
`--return-date-ranges <ranges...>`	No	Flexible return ranges, roundtrip only. Format: `YYYY-MM-DD:YYYY-MM-DD`. JSON: `return_date_ranges[]`.
`--stay-days <n>`	No	Exact stay length in days, roundtrip only. Add —trip-type roundtrip when no return dates or ranges are supplied. JSON: `stay_days`.
`--stay-days-range <min:max>`	No	Flexible stay range, e.g. `5:10`, roundtrip only. Add —trip-type roundtrip when no return dates or ranges are supplied. JSON: `stay_days_range`.
`--trip-type <type>`	No	`oneway` or `roundtrip`. Defaults to roundtrip with —return-dates or —return-date-ranges, otherwise oneway; stay-length flags alone do not change it. JSON: `trip_type`.
`--cabin-class <class>`	No	`economy`, `premium_economy`, `business`, or `first` (default: `economy`). JSON: `cabin_class`.	`"economy"`
`--direct-only`	No	Only return nonstop flights. JSON: `direct_only`.
`--adults <n>`	No	Requested adult count (default: 1); cached fares remain for one adult. JSON: `adults`.
`--children <n>`	No	Child passengers. JSON: `children`.
`--infants-in-lap <n>`	No	Infants on lap (no seat). JSON: `infants_in_lap`.
`--infants-in-seat <n>`	No	Infants in own seat. JSON: `infants_in_seat`.
`--youth <n>`	No	Youth fare. JSON: `youth`.
`--student <n>`	No	Student fare. JSON: `student`.
`--ages <ages...>`	No	Explicit ages array (alternative to counts). JSON: `ages[]`.
`--residency-country <iso2>`	No	Residency country, ISO 3166-1 alpha-2. JSON: `residency_country`.
`--max-total <amount>`	No	Upper bound on the cached fare’s total in —currency; cached fares are priced for one adult. JSON: `max_total`.
`--currency <code>`	No	ISO 4217 currency code (default: USD). JSON: `currency`.
`--locale <bcp47>`	No	BCP 47 locale, e.g. `en-US`, `fr-FR` (default: `en-US`). JSON: `locale`.
`--limit <n>`	No	Maximum destinations (1-100, default 20). JSON: `limit`.	`"20"`
`--offset <n>`	No	Pagination offset (default 0). JSON: `offset`.
`--flights-per-destination <n>`	No	Itineraries per destination (1-10, default 1). JSON: `flights_per_destination`.
`--sort-by <strategy>`	No	`lowest` or `recommendation` (default: `lowest`). JSON: `sort_by`.	`"lowest"`
`--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`.

Examples

Discover destinations reachable from your origins within a budget and date window:

jinko find-destination \
  --origins JFK LGA EWR \
  --departure-date-ranges 2027-06-01:2027-06-30 \
  --stay-days-range 5:10 \
  --trip-type roundtrip \
  --adults 2 \
  --max-total 500 \
  --currency USD

The equivalent REST and SDK calls live in the API reference.