> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gojinko.com/llms.txt
> Use this file to discover all available pages before exploring further.

# jinko hotel-cancel status

> Check how a hotel cancellation and its refund are going

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

```bash theme={null}
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`. | |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.