Skip to main content
The CLI mirrors the booking workflow exposed through MCP and is ideal for shell agents and scripts.

Install

@gojinko/cli 2.0 targets the canonical jinko-api /v1 surface. Upgrading is opt-in: the 1.x line keeps working unchanged against the legacy routes, which stay served during the transition. Upgrade when you’re ready; nothing forces a cutover.

Authenticate

OAuth:
API key:

First request

Prices in output

CLI output is the raw API response — no conversion is applied. Most prices are integers in minor units: when a money object carries decimal_places, divide by 10 ** decimal_places to display it ({ "value": 15977, "decimal_places": 2 } is 159.77, not 15,977). Amounts without a decimal_places field (trip/checkout totals, hotel rates) are already major units. Full rules: Money & prices.

Environments (prod / sandbox)

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:
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.