jinko price-monitoring

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.

Get one cached price snapshot for a specific route and date pair, then exit. To track fare changes over time, schedule repeated calls and send notifications from your own script or agent. When status is “ok”, the response includes the cheapest cached fare for one adult and an offer token you can pass to flight-search for live pricing. When status is “stale”, there is no matching cached itinerary and no fare or offer token; retry later, or use flight-search if a live quote is needed now. A stale result does not mean there are no flights. The fare and —max-total cap do not scale with —adults. For an exact whole-trip budget check, use flight-search with —max-total and the full traveler counts. Cache-only; never triggers a live call.

Usage

jinko price-monitoring [options]

Options

Flag	Required	Description
`--origin <code>`	Yes	origin IATA code (e.g. PAR for city, CDG for airport). See —origin-type for how an untyped code is read. JSON: `origin`.
`--destination <code>`	Yes	destination IATA code (e.g. NYC for city, JFK for airport). See —destination-type. JSON: `destination`.
`--origin-type <type>`	No	how to read —origin: 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 read —destination: 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-date <date>`	Yes	departure date (YYYY-MM-DD). JSON: `departure_date`.
`--return-date <date>`	No	return date for round-trip (YYYY-MM-DD). JSON: `return_date`.
`--adults <n>`	No	requested adult count (default: 1), echoed in the response only; the cached fare and cap remain for one adult. JSON: `adults`.
`--cabin-class <class>`	No	cabin class: economy, premium_economy, business, first. JSON: `cabin_class`.
`--direct-only`	No	only consider direct flights. JSON: `direct_only`.
`--max-total <amount>`	No	upper bound on the cached fare’s total; cached fares are priced for one adult. JSON: `max_total`.
`--include-carriers <codes...>`	No	whitelist IATA 2-letter carrier codes (e.g. AF KL). JSON: `include_carriers`.
`--exclude-carriers <codes...>`	No	blacklist IATA 2-letter carrier codes (e.g. FR U2). JSON: `exclude_carriers`.
`--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

# Plain poll for the cheapest cached PAR → NYC.
jinko price-monitoring --origin PAR --destination NYC \
  --departure-date 2027-06-17 --return-date 2027-06-26 --format json

# Cron entry: poll every 6 hours, alert on a hit.
# 0 */6 * * *
jinko price-monitoring --origin PAR --destination NYC \
    --departure-date 2027-06-17 --return-date 2027-06-26 \
    --direct-only --cabin-class economy --max-total 800 \
    --format json | jq -e '.status == "ok"' \
  && /usr/local/bin/notify-on-price-drop.sh

Introduction

Travel Demand

Flights

Hotels

Cars

Trip & Payment

Marketing claim

Account & utilities

Usage

Options

Examples

​Usage

​Options

​Examples

Usage

Options

Examples