Skip to Content

Changes for page 1. SearchTourPackages

Last modified by Giorgi Mdivnishvili on 2025/10/22 15:30
From version 53.1
edited by Giorgi Mdivnishvili
on 2025/10/22 13:39
Change comment: There is no comment for this version
To version 44.1
edited by Giorgi Mdivnishvili
on 2024/04/16 18:52
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -8,7 +8,7 @@
8 8  
9 9  Tour package mean, tour with hotel and flight  together In case of variation also with transfer option. Using this method gives data about full package availability with flight and hotel options.
10 10  
11 -It's possible to receive data as current dates, also in date ranges using parameter  "nights": 0,   "nightsTo ": 0. the maximum difference between the days can be 7. Below you can see examples.
11 +It's possible to receive data as current dates, also in date ranges using parameter  "stayDays": 0,   "stayDaysTo": 0. the maximum difference between the days can be 7. Below you can see examples.
12 12  
13 13  
14 14  in more  details:
... ... @@ -18,27 +18,14 @@
18 18  **Data Retrieval Parameters:**
19 19  
20 20  * **Parameter Usage**: To query package data, the system utilizes the following parameters within the request payload:
21 -** nights: Defines the minimum duration of stay (in days) as part of the tour package. The value is set to 0 by default, indicating no minimum duration constraint.
22 -** nightsTo: Specifies the maximum duration of stay (in nights) allowable within the package offerings. A default value of 0 implies no maximum limit; however, the system enforces a maximum duration difference of 7 days between nights and nightsTo.(((
23 -=== ===
24 -)))
21 +** stayDays: Defines the minimum duration of stay (in days) as part of the tour package. The value is set to 0 by default, indicating no minimum duration constraint.
22 +** stayDaysTo: Specifies the maximum duration of stay (in days) allowable within the package offerings. A default value of 0 implies no maximum limit; however, the system enforces a maximum duration difference of 7 days between stayDays and stayDaysTo.
25 25  
26 -**Date Parameters**
27 -
28 -* **checkInDate** — the date when the guest checks into the hotel.
29 -* **checkOutDate** — the date of departure from the hotel (the last day of stay).
30 -* (((
31 -If only these two parameters are specified during the search, the system will automatically select flight options that correspond to the hotel stay dates.
32 -
33 -In cases where a user wants a longer trip — for example, a **10-day tour** with only **5 days at the hotel** — they can specify flight dates (**departureDate** and **returnDate**) separately from hotel stay dates (**checkInDate** and **checkOutDate**).
34 -)))
35 -
36 -
37 37  **Constraints:**
38 38  
39 -* The system imposes a constraint wherein the difference between nights and nightsTo cannot exceed 7 days. This limit is designed to refine search results and maintain query performance.
26 +* The system imposes a constraint wherein the difference between stayDays and stayDaysTo cannot exceed 7 days. This limit is designed to refine search results and maintain query performance.
40 40  
41 -**Example Requests:** Below are examples illustrating how to structure requests for retrieving tour package data, utilizing the nights and nightsTo parameters to define the desired range of stay durations.
28 +**Example Requests:** Below are examples illustrating how to structure requests for retrieving tour package data, utilizing the stayDays and stayDaysTo parameters to define the desired range of stay durations.
42 42  
43 43  (Note: Actual example requests are not included in this response but should typically be provided here, showcasing the structure and format of API calls or query parameters used to fetch the tour package data.)
44 44  
... ... @@ -79,8 +79,8 @@
79 79   "checkInDate": "2023-12-14",
80 80   "checkInDateTo": "2023-12-14",
81 81   "checkOutDate": "2023-12-14",
82 - "nights": 0,
83 - "NightsTo": 0,
69 + "stayDays": 0,
70 + "stayDaysTo": 0,
84 84   "departureDate": "2023-12-14",
85 85   "returnDate": "2023-12-14",
86 86   "airlineCode": "string",
... ... @@ -139,8 +139,8 @@
139 139   "checkInDate": "2024-02-05T20:00:00.000Z",
140 140   "checkInDateTo": "2024-02-10T20:00:00.000Z",
141 141  
142 - "nights": 3,
143 - "nightsTo": 6,
129 + "stayDays": 3,
130 + "stayDaysTo": 6,
144 144  
145 145   "airlineCode": "",
146 146   "ticketType": "",
... ... @@ -190,6 +190,7 @@
190 190   "userErrorDescription": "string",
191 191   "packages": [
192 192   {
180 + "cacheKey": "string",
193 193   "id": "string",
194 194   "priceCurrency": "string",
195 195   "totalPrice": 0,
... ... @@ -364,6 +364,7 @@
364 364  {
365 365   "packages": [
366 366   {
355 + "cacheKey": "c705ab31e00e4f9a81c2fd46b2cdbb47f6fd9a6e16984236beb979b31aefafa4:{79}:i:10",
367 367   "id": "tour:b01c168e-2ea7-4ea6-b6e0-55abb8cab0a0:da894a1e-88c0-4877-b216-0eeeabe186f3:4298d06f-4344-4a39-ad98-071b7760cf30",
368 368   "priceCurrency": "USD",
369 369   "totalPrice": 1033.53,
... ... @@ -524,6 +524,8 @@
524 524  nullable: true
525 525  |packages|[
526 526  nullable: trueTourPackage{(((
516 +|cacheKey|string
517 +nullable: true
527 527  |id|string
528 528  nullable: true
529 529  |priceCurrency|string
... ... @@ -800,10 +800,10 @@
800 800  |arrivalLocations|array|An array of objects, each representing an arrival location. Each object contains: type (string) - The type of the location. This can be "city". label (string) - The name of the location. value (string) - The unique identifier for the location. tag (string) - A tag for the location.
801 801  |checkInDate|string|The check-in date in ISO 8601 format.
802 802  |checkInDateTo|string|The latest possible check-in date in ISO 8601 format.
803 -|nights|integer|The minimum number of days to stay.
804 -|nightsTo|integer|The maximum number of days to stay.
794 +|stayDays|integer|The minimum number of days to stay.
795 +|stayDaysTo|integer|The maximum number of days to stay.
805 805  |airlineCode|string|The code of the airline. This field can be empty.
806 -|ticketType|string|The type of the ticket. This field can be empty. definition of avia tickets classes. enum: F - First, B - Business, P = Premium, C - Coach
797 +|ticketType|string|The type of the ticket. This field can be empty.
807 807  |directFlightsOnly|boolean|Indicates whether to search for direct flights only.
808 808  |longConnectTime|boolean|Indicates whether to include flights with long connection times.
809 809  |adults|integer|The number of adults.
... ... @@ -831,6 +831,7 @@
831 831  (% class="table-bordered" %)
832 832  |=Field|=Type|=Description
833 833  |packages|array|An array of packages available. Each package contains:
825 +|cacheKey|string|A unique identifier for the cache.
834 834  |id|string|A unique identifier for the package.
835 835  |priceCurrency|string|The currency in which the price is displayed. examples -  •   KZT - ₸ •   USD - $ •   RUB - ₽ •   EUR - € •   UZS - ЛВ •   AZN - ₼
836 836  |totalPrice|float|The total price of the package.
... ... @@ -1017,6 +1017,7 @@
1017 1017  1. **FB (Full Board)**: Under the full board plan, accommodation and all three meals (breakfast, lunch, and dinner) are included. This plan is convenient for guests who do not wish to worry about arranging meals during their stay.
1018 1018  1. **AL (All Inclusive)**: The all-inclusive meal plan includes accommodation, all meals (breakfast, lunch, dinner), and usually includes a range of snacks and beverages (both alcoholic and non-alcoholic). It is the most comprehensive meal plan, offering the greatest convenience and predictability in costs.
1019 1019  
1012 +
1020 1020  **ticketType **definition of avia tickets classes.
1021 1021  
1022 1022  enum: F - First, B - Business, P = Premium, C - Coach.