API delivery for Itineraries
With Itineraries, you can display your customers’ booking information and help them find booking-related products or services such as tours or experiences. You can also use the data to analyze booking trends and create reports for your stakeholders.
Delivery options
Your API delivery of Itineraries data can use either a push or pull mechanism.
Push mechanism
The push service has been designed to send itinerary updates as they become available in near-real time, focusing on core transaction-level details. This option allows you to:
- Display customers’ booking information on your website or app
- Offer your customers additional products and services to purchase for their trip
Push events will be delivered via a Webhook to the URL you provide, in the format of an HTTP POST
message. These messages may arrive unordered, so refer to the creation_date
and update_date_time
elements to determine order.
For details on how to adopt this delivery option, see API setup.
Pull mechanism
The pull service provides detailed itinerary data to support:
- Data analysis
- Data retrieval for time windows where the push delivery failed
- Help desk investigations
This service consists of two HTTP GET
endpoints that allow you to:
- Create a list of itineraries created or updated in a specified time range using the
creation_date_start
,creation_date_end
,update_date_time_start
, andupdate_date_time_end
variables - Retrieve specific itineraries by their
itinerary_id
For details on the authentication process, see API setup.
Available fields
The tables below list the fields, including any nested objects, available through our push and pull delivery methods.
Field names that begin with a name followed by a period (for example, <variable>.<nested variable>) indicate a nesting relationship.
White Label Template
Field name | Definition | Example |
---|---|---|
itinerary_id | The itinerary number or point of sale order reference number. | 72622069245694 |
status | The status of the itinerary and of its individual items. | Possible values: confirmed cancelled |
creation_date * | The date a booking was initially made, represented in ISO 8601 date format (YYYY-MM-DD). | 2023-02-05 |
update_date_time * | The last update date and time for the itinerary, represented in ISO 8601 date format (YYYY-MM-dd"T"HH:mm:ss.SSSZ). | 2023-10-21T00:00:00.000Z |
online | Indicates whether the itinerary was booked online (true) or via an agent (false). Represented as a Boolean. | true |
package | Indicates whether the itinerary is a part of a package or a standalone booking. Represented as a Boolean. | false |
payment_type | The means of payment used at checkout. | Possible values: credit card points split pay |
point_of_sale_country_code | The country code for the point of sale from which the customer made the booking. Represented in two-letter ISO 3166-1 alpha-2 format. | GB |
purchaser | Identification of the person who made the booking. See purchaser table for listing of nested items. | |
property_booking_items | Lodging components booked as part of the itinerary. See property_booking_items table for listing of nested items. | |
flight_booking_items | Air components booked as part of the itinerary. See flight_booking_items table for listing of nested items. | |
car_booking_items | Car components booked as part of the itinerary. See car_booking_items table for listing of nested items. | |
activity_booking_items | Activity components booked as part of the itinerary. See activity_booking_items table for listing of nested items. | |
insurance_booking_items | Insurance components booked as part of the itinerary. See insurance_booking_items table for listing of nested items. | |
rate | The rate and pricing details of a booking item or of the whole itinerary. See rate table for listing of nested items. | |
coupon | The coupon applied to the itinerary, when applicable. See coupon table for listing of nested items. |
Notes for all White Label Template fields
* Date fields are in Coordinated Universal Time (UTC).
** This represents Personally Identifiable Information (PII) data. Be sure to handle this correctly per your company’s guidelines. Please include only when absolutely necessary.
*** Data for these fields will be made available between 6:00 PM and 8:00 PM UTC on the day after the booking was created or updated. Not currently available in near-real time.
Travel Agent Affiliate Program (TAAP)
Field name | Definition | Example |
---|---|---|
itinerary_id | The itinerary number or point of sale order reference number. | 72622069245694 |
status | The status of the itinerary and of its individual items. | Possible values: confirmed cancelled |
creation_date * | The date a booking was initially made, represented in ISO 8601 date format (YYYY-MM-DD). | 2023-02-05 |
update_date_time * | The last update date and time for the itinerary, represented in ISO 8601 date format (YYYY-MM-dd"T"HH:mm:ss.SSSZ). | 2023-10-21T00:00:00.000Z |
online | Indicates whether the itinerary was booked online (true) or via an agent (false). Represented as a Boolean. | true |
point_of_sale_country_code | The code for the country in which the customer made the booking. Represented in two-letter ISO 3166-1 alpha-2 format. | GB |
purchaser | Identification of the person who made the booking. See purchaser table for listing of nested items. | |
agency | Identification of the TAAP agency and agent who made the booking. See agency table for listing of nested items. | |
payment | Payment information for the itinerary. See payment table for listing of nested items. | |
property_booking_items | Lodging components booked as part of the itinerary. See property_booking_items table for listing of nested items. | |
flight_booking_items | Air components booked as part of the itinerary. See flight_booking_items table for listing of nested items. | |
car_booking_items | Car components booked as part of the itinerary. See car_booking_items table for listing of nested items. | |
activity_booking_items | Activity components booked as part of the itinerary. See activity_booking_items table for listing of nested items. | |
rate | The rate and pricing details of a booking item or of the whole itinerary. See rate table for listing of nested items. | |
earnings | The commission details of a booking item or of the whole itinerary. See earnings table for listing of nested items. |
Notes for all TAAP fields
* Date fields are in Coordinated Universal Time (UTC). ** This represents Personally Identifiable Information (PII) data. Be sure to handle this correctly per your company’s guidelines. Please include only when absolutely necessary. *** Data for these fields will be made available between 6:00 PM and 8:00 PM UTC on the day after the booking was created or updated. Not currently available in near-real time.
API details
We’ve provided a snapshot of the API schema and configurations based on how your business would use Itineraries API data. You can download the OpenAPI specifications and use an API testing software to get an understanding of how the examples and schema definitions compare to the actual output.
White Label Template
The fields, including any nested objects, available to our White Label Template partners through our push and pull delivery methods are:
TAAP
The fields, including any nested objects, available to our TAAP partners through our push and pull delivery methods are: