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 51.1
edited by Giorgi Mdivnishvili
on 2025/10/22 13:06
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -19,26 +19,13 @@
19 19  
20 20  * **Parameter Usage**: To query package data, the system utilizes the following parameters within the request payload:
21 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 -)))
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 nightsand nightsTo.
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 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.
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  
... ... @@ -800,8 +800,8 @@
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.
790 +|stayDays|integer|The minimum number of days to stay.
791 +|stayDaysTo|integer|The maximum number of days to stay.
805 805  |airlineCode|string|The code of the airline. This field can be empty.
806 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
807 807  |directFlightsOnly|boolean|Indicates whether to search for direct flights only.