Install
Authenticate
Use an API key. OAuth login is deprecated. Save a key for the selected environment:JINKO_API_KEY takes precedence over saved keys, even when you switch environments with --env. Use a key for the selected environment, or unset the variable to use saved profiles.
First request
Prices in output
CLI output is the raw API response, and no conversion is applied. Read money from the*_money fields (and value on objects that carry it): value is an
integer in minor units, so divide by 10 ** decimal_places to display it
({ "value": 15977, "decimal_places": 2 } is 159.77, not 15,977), or show
display. The older fields beside them, such as trip and checkout
total_amount and hotel total_amount, are deprecated and hold major units.
Full rules: Money & prices.
Environments
The CLI targets production by default. Use--env sandbox to run the full flow against the sandbox environment (isolated data, separate API keys) before going live:
Use Jinko Airline (ZZ) for sandbox flight tests: include_carriers: ["ZZ"] on JFK–LHR from tomorrow onwards, and flight ZZ101 for the normal flow. It is a fake airline that exists only in sandbox and always behaves the same way; each other flight number triggers one documented behaviour, including failures. With include_carriers: ["ZZ"] the results are Jinko Airline only. An empty result means no Jinko Airline itinerary matched the route, date and other filters you sent (times, cabin, stops, price): read the instruction and adjust one filter. See Testing in sandbox for routes, prices and scenarios, and sandbox flight coverage for real airlines.
Prod and sandbox keys are stored separately in
~/.jinko/config.yaml, so you keep both and switch with --env. JINKO_ENV=sandbox and the raw JINKO_API_BASE override also work.