Packages integration technical requirements

Hotel Static info

As a basis for Package integration, Skyscanner need download the complete Package hotel static information from the partner website before integration.
Inventory should be accesible via HTTPS API or downloadable files through HTTPS or FTP protocols.
Accepted files formats: csv, xml, json
mandatory fields:

• hotel_name
• street_address
• location (coordinates)
• country code
   

Package availability request:

Preferred integration method is via API supporting query quotation by hotelIds. As a standard we expect following fields to be supported.
 

• origin IATA
• destination IATA
• departure date
• return date
• HotelIds
• number of travellers (Number of adults and children specifying where possible the ages of the children)
• Desired language
• Desired currency

• market

Response

Please see below a list of required fields (downloadable document attached).
Presented hierarchical structure is just an example. We can work with other formats as long as all the required information is provided.

L1	L2	L3	L4	L5	L6	description	required
package_quotes	attributes					product labels, e.g. ATOL protected	Optional
	price	total_price	currency_code			the total price for all travel travels	Yes
			amount
			unit
	discount_price	total_price	currency_code			it’s the saving price	Optional
			amount
			unit
	deeplink_datum	fields	signature			the deeplink info which clear know how to redirect to partner Package website, it also OK if partner can provide the detail of how to build the deeplink	Yes
		url
		form_data
	hotel_terms	rooms[]	meal_plan			like room only, breakfast included，full meal include…	optional
			occupancy			how many people occupancy for this room	Yes
			count			the count of the room	Yes
package_itinerary	hotel_itineraries	hotel	location_reference_type			partner should provide the partner-hotelid in the response, we will mapping it to skyscanner entityid	Yes
			id
		checkin_date	year			hotel check-in date, it different from the flight departure date, It‘s the clear hotel checkin date	Yes
			month
			day
		checkout_date	year			hotel check-out date, it different from the flight return date, It‘s the clear hotel checkout date	Yes
			month
			day
	transport_itinerary	legs[0] - outbound legs[1] - inbound	segment	origin	location_reference_type	it is the departure airport IATA code, like LON	Yes
					id
				destination	location_reference_type	it is the arrival airport IATA code, like BCN	Yes
					id
				departure	year	datetime detail of the departure and arrival, we need calculate the flight duration base on these datetime	Yes
					month
					day
					hour
					minute
				arrival	year		Yes
					month
					day
					hour
					minute
				marketing_carrier_transport_reference		flight number	Yes
				marketing_carrier_id		2 letters flight IATA code, we can also extract from flight number	Yes
				operating_carrier_id			Yes
				transport_mode		Flight/Rail… default is flight	Optional
				connection		how to transfer when the flight is not direct	Optional