jinko hotel-cancel commit

Start the cancellation a preview described, once the customer has agreed to its refund. Send the same —booking-ref, —booked-item-id and —last-name as the preview. A 409 cancels nothing: QUOTE_DRIFT (show the customer current.refund, then commit again with the retry_quote_id and that figure, or preview again when no retry_quote_id is given), QUOTE_EXPIRED (preview again), ACTIVE_OPERATION_EXISTS (poll the operation already running), NOT_CANCELLABLE, FUNDS_UNAVAILABLE. Success answers an operation handle: the refund has not moved yet; follow it with hotel-cancel status.

Usage

jinko hotel-cancel commit [options]

Options

Flag	Required	Description
`--booking-ref <ref>`	Yes	Jinko booking reference from get-booking. JSON: booking_ref.
`--last-name <name>`	No	Lead guest surname, required for guest lookup; owning credentials may omit it. JSON: last_name.
`--booked-item-id <id>`	No	The booked item to service: booked_item_id from get-booking items[] (an “itm_…” string); required when several items of this domain exist. JSON: booked_item_id.
`--quote-id <id>`	Yes	the “svq_…” quote_id returned by hotel-cancel preview. JSON: quote_id.
`--acknowledged <amount>`	Yes	the preview refund object verbatim as JSON, the figure the customer agreed to; its amount_money is sent, else its inline value/currency/decimal_places: {“amount_money”:{“value”:45000,“currency”:“EUR”,“decimal_places”:2},…}. JSON: acknowledged.
`--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`.

Introduction

Travel Demand

Flights

Hotels

Cars

Trip & Payment

Marketing claim

Account & utilities

Usage

Options

​Usage

​Options

Usage

Options