Skip to main content
GET
Fetch the full lifecycle state of a trip — items, travelers, quote, fulfillment, and any booking references
Inspect the current state of a trip without modifying it. Reach for it when you need to confirm what items are on the trip, verify the travelers attached to a booking, or check whether a checkout has finalized after the user paid. The response covers items, traveler details, the quote and its quote_id, the booking’s progress in booking_state once payment starts, and any booking references that have been issued. This read does not start pricing. Checkout starts pricing and waits for success or failure. If quote.status is failed, no payable quote was established, even if an older response also carries expires_at. Failed quotes omit expires_at and can include failure_reason and failure_message. For offer_expired or offer_unavailable, search again and replace the item before checking out. A missing item price_money or total_amount_money means the figure is not known yet and must not be displayed as zero. status is one value for the whole trip. Once payment starts, booking_state summarizes the booking and fulfillment.status gives the detailed status behind it. See Trip status and booking state.

Authorizations

​
X-API-Key
string
header
required

Path Parameters

​
trip_id
string
required

Response

The trip

​
trip_id
string
required
Example:

"trip_1048576"

​
seat_map_url
string

Link to a page where the traveller picks seats on a visual seat map. Present only when a flight item has a seat-map session. Expires; read the trip again for a fresh link.

​
payment_attempt
object
​
status
enum<string>

Where the trip is in its lifecycle, as one value for the whole trip. The booking’s progress after payment is booking_state (GET /v1/trip/{trip_id}); the four booking values below (fulfilling, fulfilled, partially_fulfilled, failed) are deprecated in favour of it and still sent. draft: being built or priced, nothing paid. fulfilling: payment was submitted and booking started. Then exactly one outcome: fulfilled (booking_state completed), partially_fulfilled (partial) or failed (failed). cancelled: replaced by a new trip when it was re-shopped. expired is the 24-hour lapse: it is evaluated LAZILY, on the read that first observes it, so this call is where a dead trip becomes visible. Once a trip is expired, adding items, setting travelers and checkout are refused with TRIP_EXPIRED; any other state that refuses a write answers TRIP_STATE_CONFLICT and names the state here. Start a new trip — a lapsed one cannot be revived. quoting, quoted and fulfillment_prepared are reserved and not currently set; quote progress is in quote.status.

Available options:
draft,
quoting,
quoted,
fulfillment_prepared,
fulfilling,
fulfilled,
partially_fulfilled,
failed,
cancelled,
expired
Example:

"draft"

​
travelers
object[]
​
contact
object
​
hotel_room_guests
object

Optional primary adult room-contact overrides keyed by the returned hotel item_id/product_id. Each product array is non-empty and occupancy_number values are unique positive room slots; omitted slots use persisted adult travelers in order with the trip contact email. The trip must already exist because the keys refer to its items.

​
items
object[]
​
total_amount
object
deprecated

Deprecated: use total_amount_money instead. The trip total in major currency units.

​
total_amount_money
object

The trip total. Absent until the trip has been quoted.

​
quote
object

Latest pricing attempt. POST /v1/trip does not start pricing; POST /v1/checkout starts it and waits for success or failure. Reading the trip does not trigger pricing. A failed quote has no payable price.

Example:
​
fulfillment
object
​
booking_state
enum<string>

The booking’s progress once payment has started; absent before. awaiting_payment: waiting for the payment to be confirmed. processing: booking with the suppliers. Then one outcome: completed (every item booked), partial (some items booked), failed (nothing booked) or cancelled. needs_review: held for a person at Jinko to resolve; not final. fulfillment.status keeps the detailed status behind it.

Available options:
awaiting_payment,
processing,
completed,
partial,
failed,
cancelled,
needs_review
Example:

"processing"

​
booking_ref
string

The Jinko booking reference for this trip — the value POST /v1/get_booking, cancel, refund and exchange take as booking_ref, and the booking_ref every webhook event carries. Present as soon as booking has been scheduled for the trip, which can be before payment completes (a hosted checkout still in progress, or an agent submit that fell back to checkout_url, leaves the booking awaiting_payment). Presence does not mean paid: read booking_state. The value never changes afterwards. One per trip.

Example:

"JNK-XEVGW5"

​
bookings
object[]

One entry per item with a booking reference, including items whose booking was attempted and failed. The supplier confirmation can be empty on failed items; the Jinko reference is the trip-level booking_ref.

​
created_at
string
Example:

"2026-06-01T12:30:00Z"

​
updated_at
string
Example:

"2026-06-01T12:34:56Z"