<TOUR>
required
A tag within which everything else is. The root tag is .
<CURRENCY_ID>
required
This tag contains ISO code of the currency. We always display prices in Czech crowns, it is necessary to write the tag in this form:
<currency_id>CZK</currency_id>
<TOUR_ID>
required
A tag identifying a unique ID generated by a travel agency. In each export and subsequent update, the same ID must be kept for a specific tour. If the ID changes in the new export, the tour will be considered different. The ID value must contain only alphanumeric characters.
<TOUR_TYPE>
A tag indicating the type of tour (seaside, sightseeing, active skiing, etc.). Values according to the attached codebook.
<TOUR_DETAIL_URL>
required
A tag defining a link to a travel agent’s website describing general information about the tour (hotel).
<LOCATIONS>
required
A tag defining the location of the tour, i.e. the country, region and place. This mark includes:
<location>
<!-- ISO country code according to the codebook, in this case Turkey -->
<country_id>TUR</country_id>
<!-- text name of the region, must not be the same as the country name -->
<area_title>Antalya</area_title>
<!-- text place name, must not match the area name -->
<place_title>Kumkoy Beach</place_title>
</location>
<TOUR_TITLE>
required
A tag defining the name of the tour. Use alphanumeric characters only, limit 80 characters including spaces. The tour name must not contain price, meals, stars, exclamation marks or advertising elements (“special offer”, etc.).
<TOUR_DESC>
required in the absence of other descriptions (accommodation_desc, location_desc, program)
A tag defining the description of the tour.
<ACCOMMODATION>
required
A tag that defines the accommodation. The following fall under this tag:
<accommodation>
<type />
<class_id />
<title />
<gps />
<location_descs />
<accommodation_desc />
</accommodation>
<TYPE>
A tag defining the textual name of the accommodation type. If the tour is without accommodation, enter “Without accommodation”. Use only alphanumeric characters and punctuation marks. Example:
<type>Hotel</type>
<CLASS_ID>
required
A tag indicating the number of stars. Enter the value 1-11. Example 5*+:
<class_id>11</class_id>
<TITLE>
required
A tag defining the name of the accommodation. The name may not contain stars or price. Example:
<title>Sun Island Resort & Spa</title>
<GPS>
A tag specifying GPS coordinates in Latitude/Longitude format. If GPS coordinates are used, the tour will be enriched by the map base and has a significantly better chance of being relevant to the user. Example:
<gps>
<lat>60.2233</lat>
<lon>114.1234</lon>
</gps>
<LOCATION_DESCS>
povinný v případě absence ostatních popisů (tour_desc, accommodation_desc, program)
Značka popisující lokalitu ubytování. Pod tuto značku spadá <location_desc>, který může být obohacen o příznak Title. V případě více popisů v rámci značky je příznak Title povinný. Příkladem:
<LOCATION_DESCS>
required in the absence of other descriptions (tour_desc, accommodation_desc, program)
A tag describing the location of the accommodation. This tag includes <location_desc>, which can be enriched by the Title flag. In case of multiple descriptions within a tag, the Title flag is mandatory. Example:
<location_descs>
<location_desc title="Location">The hotel is located in a quiet area 200m from the sea and 500m from the town centre.</location_desc>
<location_desc title="Environment">The hotel is situated close to a beautiful park full of local fauna and flora.</location_desc>
</location_desc>
<ACCOMMODATION_DESCS>
required in the absence of other descriptions (tour_desc, location_desc, program)
A tag describing room amenities and accommodation options. In case of multiple descriptions within a tag, the Title flag is mandatory.
<accommodation_descs>
<accommodation_desc title="Facilities">The hotel was renovated in 2022 to meet the requirements of even the most demanding customers. Facilities include a swimming pool, gym and children's playroom.</accommodation_desc>
</accommodation_descs>
<PHOTOS>
required
The defining mark of the tour photo. This tag must be followed by the order, a link to the URL of the photo and a description of the photo for each photo. The first photo in the sequence is the main photo.
- The URL of the photo must be encoded (do not use diacritics, spaces, abbreviated forms of ampersands).
- Photos must show places associated with the tour.
- Photos must be in JPG, PNG, WEBP, AVIF format. Maximum photo size 2MB.
- Photos must have a size of at least 400x300 pixels. We recommend using standard aspect ratio, i.e. 4:3, 16:9 or panoramic 4:1, 10:1.
- The photo must not include advertising slogans, advertising or other distinctive graphic elements.
- Each photograph must be unique within the tour.
<photos>
<photo>
<!-- tag defining the order of the photo -->
<order>1</order>
<!-- tag defining the link to the photo -->
<url>http://www.example.com/img1.jpg</url>
<!-- tag defining the description of the photo -->
<desc>Hotel entrance</desc>
</photo>
<photo>
<order>2</order>
<url>http://www.example.com/img2.jpg</url>
<desc>Hotel swimming pool</desc>
</photo>
</photos>
<TERM_GROUPS>
required
A tag indicating the tour options. Under this tag you can find all the tour variants that the tour contains. A tour may not contain more than one tour variant with the same meals, transport and departure points. Multiple tour variants with the same transport and meals must not repeat the same departure points.
<term_groups>
<term_group /> <!-- 1st tour option --><term_group /> <!-- 2nd tour option -->
</term_groups>
<TERM_GROUP>
required
A tour variant tag that defines a group of dates with the same transport, meals and departure points (maximum 10). A tour variant contains the following tags:
<term_group>
<!-- tag defining the diet, value 1-8 according to the codebook -->
<board />
<!-- tag defining transport, value 1-6 according to the codebook -->
<transport />
<!-- tag defining departure or arrival points, always city specific -->
<dept_places />
<!-- tag describing information about what is included in the final price -->
<terms />
</term_group>
<TERMS>
required
A tag defining the individual dates in a given tour option. The date ID is unique within one tour variant. The ID of a specific date must be preserved across the XML generation. The date must be available for booking or enquiry on the travel agent’s website.
The structure of XML terms is as follows:
<terms>
<term>
<!-- tag identifying the ID generated by the travel agency -->
<id>111111<id/>
<!-- tag defining the start of the term, must be earlier than the end date -->
<start>2013-07-14</start>
<!-- marker defining the end of the date, must be later than the start date -->
<end>2013-07-22</end>
<!-- tag defining the number of days, must be greater than zero and the number of nights -->
<day_count>9</day_count>
<!-- tag specifying the number of nights, must be zero or more -->
<night_count>8</night_count>
<prices>
<price>
<desc_id />
<final_price />
</price>
</prices>
<purchase_url />
</term>
</terms>
<PRICES> / <PURCHASE_URL>
required
Price items :
A tag defining the individual price items for a given term, including the type of person, final price, and a link to the order form or inquiry. The price must always be for the term to which it relates. Must include all mandatory surcharges and taxes. The price per adult can only be one per term and must be the same as the price for the first person. The price per adult must always be defined and must be greater than 0. If the price per child is 0, it is considered “free”.
Link to the order form <purchase_url>:
The landing page must allow users to book, reserve or enquire about a given appointment. The page must contain the name of the selected tour, the selected date, transport and meals with the same price as the one in the XML file.
The structure of XML price items is as follows:
<terms>
<term>
<id />
<start />
<end />
<day_count />
<night_count />
<!-- price section tag -->
<prices>
<!-- term price item tag -->
<price>
<!-- price description ID according to the codebook; 1 - adult, 2 - child, 3 - senior -->
<desc_id>1</desc_id>
<!-- tag indicating the final price per person -->
<final_price>15000</final_price>
</price>
</prices>
<!-- link to the script that verifies the availability of the date -->
<availability>http://www.ck.cz/dostupnost.php?termin=12345</availability>
<!-- link to the booking or enquiry form of the given date at the CK -->
<purchase_url>http://www.ck.cz/objednavka.php?termin=12345</purchase_url>
</term>
</terms>```