Get Booking

Start here before flight_refund, flight_exchange, hotel_cancel or car_cancel. Retrieve a booking by its Jinko booking_ref, then choose the intended items[] entry.

Each item has a stable booked_item_id (an "itm_…" string), itinerary summary, confirmation, supplier_references (the confirmations the airline, hotel or rental company issued), status and servicing eligibility: can_refund, can_void, can_exchange, refund_support_level, exchange_support_level and refusal reasons/reason_code. Use booking_ref + that booked_item_id on every subsequent servicing action. Keep the same booked_item_id after an exchange. booking_state summarizes the booking's progress after payment.

last_name is required for guests and optional for an authenticated owner. No login is needed for guest lookup.

USAGE: get_booking({ booking_ref: "JNK-A7B3X9", last_name: "Doe" })

booking_ref is the JNK-XXXXXX reference from the confirmation email, get_trip or submit_agent_payment. The airline record locator (pnr) in a flight item's supplier_references is for airline check-in; servicing uses booking_ref + booked_item_id.

Parameters

Name	Type	Required	Description
`booking_ref`	`string`	Yes	Trip-level Jinko booking_ref returned by get_trip or submit_agent_payment. Use it to look up the booking with get_booking.
`last_name`	`string \| null`	No	Primary traveler last name. Required for guests; optional for an authenticated owner of the booking.
`user_intent`	`string`	No	The end user’s current request in their own words, e.g. “help me with my travel plans”. Pass it as-is when short; otherwise condense the goal and constraints into 1-2 sentences. Strip personal identifiers (names, emails, phone numbers, addresses, payment details), replace them with placeholders like “[name]”. Optional. Jinko uses it to understand demand, and hotel_search uses it to rank hotel results against what the user asked for (e.g. “quiet, with a gym, near Times Square”), so keep the user’s stated preferences in it.

Examples

Guest lookup by Jinko reference + last name:

{
  "name": "get_booking",
  "arguments": {
    "booking_ref": "JNK-ABC123",
    "last_name": "Doe"
  }
}

Returns the booking envelope (itineraries, travelers, status). The MCP connection still requires authentication. Guest lookup verifies the booking reference and last name, so travelers do not need a personal Jinko login.

Error handling:

MCP returns structuredContent.status: "not_found" for an unknown or inaccessible booking, including a last-name mismatch. It deliberately does not reveal whether the booking exists. Ask the user to check the reference and last name rather than retrying with variations.

Introduction

Flights

Hotels

Cars

Trip & Payment

Marketing claim

Parameters

Examples

​Parameters

​Examples

Parameters

Examples