jinko hotel-search

Read amounts from the *_money fields in this command’s output, such as rates[].total_amount_money. Each carries value in minor units with its decimal_places: divide value by 10 ** decimal_places, or show display. The older fields beside them (total_amount, taxes_breakdown[].amount, cancellation_schedule[].amount) are deprecated and hold major units. See Money & prices.

Search live hotel inventory and nightly rates for a destination and stay window. It handles requests like “three nights in Lisbon next weekend for two adults” or “family room in Rome with one child in August”. Choose an offer from hotels[].offers[] and pass its offer_id to jinko trip --trip-item-token to start a booking.

Usage

jinko hotel-search [options]

Options

Flag	Required	Description	Default
`--query <text>`	No	unambiguous city or well-known POI only. For regions, use —latitude + —longitude or —city-name + —country-code. Mode B. JSON: `query`.
`--city-name <name>`	No	city name (e.g. “Paris”), Mode B destination, or Mode A lookup scope when combined with —hotel-name. JSON: `city_name`.
`--country-code <code>`	No	ISO 3166-1 alpha-2 country code (e.g. fr), Mode B destination, or Mode A lookup scope when combined with —hotel-name. JSON: `country_code`.
`--latitude <latitude>`	No	latitude for geo-radius search, Mode B. JSON: `latitude`.
`--longitude <longitude>`	No	longitude for geo-radius search, Mode B. JSON: `longitude`.
`--radius-km <km>`	No	search radius in km (default 5, max 50), Mode B. JSON: `radius_km`.
`--hotel-ids <ids...>`	No	re-shop specific hotel IDs, Mode A. JSON: `hotel_ids`.
`--hotel-name <name>`	No	look up a specific hotel by name, Mode A. Pair with —city-name and —country-code to narrow the lookup scope.
`--checkin <date>`	Yes	check-in date (YYYY-MM-DD). JSON: `checkin`.
`--checkout <date>`	Yes	check-out date (YYYY-MM-DD). JSON: `checkout`.
`--adults <n>`	No	number of adults (shorthand). JSON: `adults`.	`"2"`
`--children <ages...>`	No	children ages (shorthand, e.g. 5 7). JSON: `children`.
`--rooms <n>`	No	number of rooms (shorthand). JSON: `rooms`.
`--currency <code>`	No	ISO 4217 currency code (default USD). JSON: `currency`.
`--guest-nationality <code>`	No	guest nationality (ISO 3166-1 alpha-2). JSON: `guest_nationality`.
`--min-rating <n>`	No	minimum guest review rating (0-10). JSON: `min_rating`.
`--star-rating <n>`	No	minimum star rating (1-5). JSON: `min_star_rating`.
`--max-star-rating <n>`	No	maximum star rating (1-5). JSON: `max_star_rating`.
`--min-reviews <n>`	No	minimum number of reviews. JSON: `min_reviews`.
`--max-results <n>`	No	maximum hotels to return per page (default 50). JSON: `max_results`.
`--offset <n>`	No	pagination offset, skip this many hotels at the upstream search (default 0). JSON: `offset`.
`--max-budget-per-night <amount>`	No	keep only hotels whose cheapest per-night price (per room, in the request currency) fits this budget; the search scans deeper automatically when few hotels fit. JSON: `max_budget_per_night`.
`--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

# Paris, 2 adults, 3 nights
jinko hotel-search --query "Paris" --checkin 2027-07-15 --checkout 2027-07-18 --adults 2

# By city + country, filtered
jinko hotel-search --city-name "Barcelona" --country-code ES \
  --checkin 2027-08-01 --checkout 2027-08-05 --adults 2 \
  --min-rating 8 --star-rating 4

Introduction

Travel Demand

Flights

Hotels

Cars

Trip & Payment

Marketing claim

Account & utilities

Usage

Options

Examples

​Usage

​Options

​Examples

Usage

Options

Examples