jinko travel-demand audience - Jinko Platform

Traveler-type composition (Solo/Couple/Family/Group) of demand for a destination. —destination is required. (traveler_type is not a filter here, it is the dimension.)

Usage

jinko travel-demand audience [options]

Options

Flag	Required	Description	Default
`--origin <level:code>`	No	origin filter, e.g. Country:US or City:NYC (or ‘global’ for all origins)
`--destination <level:code>`	Yes	destination, e.g. Country:JP
`--departure-date-from <YYYY-MM-DD>`	No	start of departure window (use with —departure-date-to; omit both for no departure-date filter)
`--departure-date-to <YYYY-MM-DD>`	No	end of departure window (use with —departure-date-from; omit both for no departure-date filter)
`--trip-type <type>`	No	oneway\|roundtrip
`--trip-duration-min <n>`	No	minimum trip length in nights (round-trips only, >= 0)
`--trip-duration-max <n>`	No	maximum trip length in nights (>= —trip-duration-min)
`--search-window-min <n>`	No	minimum advance-purchase window in days before departure (>= 0)
`--search-window-max <n>`	No	maximum advance-purchase window in days (>= —search-window-min)
`--snapshot-window-days <n>`	No	days of recent search activity aggregated into the demand level (2-90, default 7)
`--limit <n>`	No	max rows, 1-200 (default 20)