Changes for page 1. SearchTourPackages

Last modified by Giorgi Mdivnishvili on 2025/02/12 15:25

From version 33.1
edited by Giorgi Mdivnishvili
on 2024/04/11 11:46
Change comment: There is no comment for this version
To version 37.1
edited by Giorgi Mdivnishvili
on 2024/04/11 17:29
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -6,11 +6,32 @@
6 6  
7 7  = Method Description =
8 8  
9 -Tour package mean, tour with hotel and flight together. Using this method gives data about full package availability with flight and hotel options.
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 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 +in more  details:
15 +
16 +A tour package encapsulates a bundled offering that includes both hotel accommodations and flight arrangements. In certain variations, it may also incorporate transfer options, providing a comprehensive travel solution. The method detailed herein facilitates the retrieval of data concerning the complete availability of such tour packages, including pertinent flight and hotel options.
17 +
18 +**Data Retrieval Parameters:**
19 +
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.
23 +
24 +**Constraints:**
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.
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.
29 +
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 +
32 +This documentation aims to guide developers in effectively querying for tour package options, employing specified parameters to tailor the search according to the duration of stay requirements.
33 +
34 +
14 14  == Endpoint URL - [POST] ==
15 15  
16 16  {{info}}
... ... @@ -862,7 +862,6 @@
862 862  |totalCount|integer|The total count of packages.
863 863  |error|boolean|Indicates whether there was an error.
864 864  
865 -
866 866  === Paging and Caching ===
867 867  
868 868  During the first request, Paging id must be  empty like this  ( "pagingId": "",)  pagenumber is the number of the page, pagerowcount means number of the given result in one page. So in the first request we can search like this:
... ... @@ -936,18 +936,18 @@
936 936  == Important ==
937 937  
938 938  {{error}}
939 -It's Important to in every other request header, put Auth token
959 +=== Implementing Authorization in Subsequent Requests ===
940 940  
941 -**Key **- Authorization
961 +For every API request after the initial authentication, it's crucial to include the authorization token in the request header. This ensures your requests are authorized and can access the necessary resources. Here's how to properly include your token:
942 942  
943 -**Value **- Bearer Token what is given in this response.
963 +* **Header Key:** Authorization
964 +* **Header Value:** Bearer [Your Token Here] - Use the bearer token provided in the initial authentication response. The authorization type should be specified as Bearer Token.
944 944  
966 +Additionally, to ensure your requests are properly formatted and recognized, include the following headers:
945 945  
946 -**also note in headers that:**
968 +* **Content-Type:** Specify this header as application/json to indicate the format of the request body.
969 +* **Header Key:** X-nugios-timezone
970 +* **Header Value:** 240 - Adjust this value to match your local timezone offset in minutes.
947 947  
948 -Content-Type - application/json
949 -
950 -**Key - **X-nugios-timezone
951 -
952 -**Value **- 240
972 +Incorporating these headers with their respective values is essential for the successful processing of your API requests.
953 953  {{/error}}