Skip to Content

Changes for page 1. SearchTourPackages

Last modified by Giorgi Mdivnishvili on 2025/10/22 15:30
From version 46.1
edited by Giorgi Mdivnishvili
on 2025/02/12 15:25
Change comment: There is no comment for this version
To version 53.1
edited by Giorgi Mdivnishvili
on 2025/10/22 13:39
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  "stayDays": 0,   "stayDaysTo": 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  "nights": 0,   "nightsTo ": 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,14 +18,27 @@
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 -** 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.
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 +)))
23 23  
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 +
24 24  **Constraints:**
25 25  
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.
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.
27 27  
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.
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.
29 29  
30 30  (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.)
31 31  
... ... @@ -66,8 +66,8 @@
66 66   "checkInDate": "2023-12-14",
67 67   "checkInDateTo": "2023-12-14",
68 68   "checkOutDate": "2023-12-14",
69 - "stayDays": 0,
70 - "stayDaysTo": 0,
82 + "nights": 0,
83 + "NightsTo": 0,
71 71   "departureDate": "2023-12-14",
72 72   "returnDate": "2023-12-14",
73 73   "airlineCode": "string",
... ... @@ -126,8 +126,8 @@
126 126   "checkInDate": "2024-02-05T20:00:00.000Z",
127 127   "checkInDateTo": "2024-02-10T20:00:00.000Z",
128 128  
129 - "stayDays": 3,
130 - "stayDaysTo": 6,
142 + "nights": 3,
143 + "nightsTo": 6,
131 131  
132 132   "airlineCode": "",
133 133   "ticketType": "",
... ... @@ -787,8 +787,8 @@
787 787  |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.
788 788  |checkInDate|string|The check-in date in ISO 8601 format.
789 789  |checkInDateTo|string|The latest possible check-in date in ISO 8601 format.
790 -|stayDays|integer|The minimum number of days to stay.
791 -|stayDaysTo|integer|The maximum number of days to stay.
803 +|nights|integer|The minimum number of days to stay.
804 +|nightsTo|integer|The maximum number of days to stay.
792 792  |airlineCode|string|The code of the airline. This field can be empty.
793 793  |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
794 794  |directFlightsOnly|boolean|Indicates whether to search for direct flights only.