jinko hotel-cancel status - Jinko Platform

Report where a committed hotel cancellation has got to, by the operation handle the commit (or the deprecated one-shot form) returned. Read-only. Keep polling while state is in_progress or attention_required. Do not tell the customer they have been refunded until money.vehicle_state is paid.

Usage

jinko hotel-cancel status [options]

Options

Flag	Required	Description	Default
`--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.
`--operation <id>`	Yes	the “svc_…” operation handle returned by hotel-cancel commit. JSON: operation.
`--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`.