Skip to main content
Jinko’s APIs are designed around a staged booking workflow.

​
Discovery versus live pricing

The cached discovery tools are optimized for speed and broad exploration. Once you have a candidate offer, switch to live pricing to confirm the fare and obtain a trip_item_token.

​
Tokens and IDs

  • offer_token identifies a candidate itinerary returned by discovery.
  • trip_item_token identifies a price-checked itinerary that can be added to a trip.
  • trip_id identifies the mutable trip/cart used for quoting, payment, and booking.

​
Hosted checkout

Jinko owns the payment surface. Your agent prepares the trip, sends the user to checkout_url, and then confirms payment to trigger booking.