Skip to Content
Last modified by Giorgi Mdivnishvili on 2025/10/22 13:39
From version 14.1
edited by Giorgi Mdivnishvili
on 2024/04/11 17:40
Change comment: There is no comment for this version
To version 7.1
edited by Giorgi Mdivnishvili
on 2024/04/11 11:05
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -SearchTourPackages - Basic Version
1 +SearchTourPackages - Basic version
Content
... ... @@ -6,32 +6,11 @@
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 9  
10 -=== Method Overview: Streamlined Tour Package Discovery and Booking ===
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 11  
12 -**Purpose:** This method outlines the most efficient process for locating and subsequently booking a tour package utilizing a minimal set of required parameters. It is designed to simplify the user interaction by reducing the complexity and volume of input data necessary for operation.
13 13  
14 -**Procedure:**
15 -
16 -1. **Initialization**: Start by specifying the essential parameters. This approach is engineered to streamline the search and booking process, focusing on the core data elements critical for identifying suitable tour packages.
17 -1. **Search Execution**: Deploy the method with the specified parameters to initiate the search. The system is optimized to process these inputs, conducting a targeted query across available tour packages to identify matches that align with the user's criteria.
18 -1. **Selection and Booking**: Upon receiving search results, the user can select a desired tour package. The booking process is then initiated with the minimal parameters already provided, ensuring a seamless transition from selection to confirmation.
19 -
20 -**Parameter Details:**
21 -
22 -* The parameters required for this method are intentionally limited to essential elements only, aiming to expedite the search and booking phases while maintaining effectiveness. Details on these parameters, including data types and usage instructions, are documented separately.
23 -
24 -**Usage Notes:**
25 -
26 -* This method is particularly beneficial for users seeking a straightforward and efficient path to tour package booking, minimizing decision fatigue and enhancing user experience.
27 -
28 -**Examples:**
29 -
30 -* Code examples and detailed step-by-step instructions for utilizing this method are available in the subsequent sections, providing practical guidance on implementing the streamlined tour package discovery and booking process.
31 -
32 -This documentation segment aims to facilitate developers and users in leveraging a simplified method for tour package exploration and booking, ensuring an efficient and user-friendly interaction with the system.
33 -
34 -
35 35  == Endpoint URL - [POST] ==
36 36  
37 37  {{info}}
... ... @@ -67,35 +67,7 @@
67 67  }
68 68  {{/code}}
69 69  
70 -== Request example for 2Adults 2Child ==
71 71  
72 -{{code language="Json"}}
73 -{
74 - "departureCountryCode": "KZ",
75 - "departureCityUID": "f0ba6324-f337-405c-8cc7-23d62cf664e8",
76 - "arrivalCountryCode": "AE",
77 - "adults": 2,
78 - "children": 2,
79 - "childrenAges": [
80 - 4,
81 - 8
82 - ],
83 - "departureDate": "2024-05-26T00:00:00",
84 - "returnDate": "2024-06-02T00:00:00",
85 - "departureAndReturnDaysCount": 7,
86 - "checkInDate": "2024-05-26T00:00:00",
87 - "checkOutDate": "2024-06-02T00:00:00",
88 - "checkInAndCheckOutDaysCount": 7,
89 - "directFlightsOnly": true,
90 - "searchCurrency": "USD",
91 -
92 - "pagingId": "",
93 - "pageNumber": 1,
94 - "pageRowCount":5
95 -}
96 -{{/code}}
97 -
98 -
99 99  == Response Body ==
100 100  
101 101  {{code language="json"}}
... ... @@ -779,6 +779,7 @@
779 779  |pageRowCount|Integer|No|The number of results to return per page. For example, 1 to return 1 result per page.
780 780  |searchCurrency|String|No|The currency in which the search results should be displayed. For example, "USD" for United States Dollar.
781 781  
733 +=== ===
782 782  
783 783  === **Response Parameters** ===
784 784  
... ... @@ -860,7 +860,6 @@
860 860  |totalCount|Number|The total count of packages. This is the total number of packages in all pages of results.
861 861  |error|Boolean|A boolean indicating whether there was an error. If true, it means that there was an error in retrieving the packages.
862 862  
863 -
864 864  ==== first request ====
865 865  
866 866  {{code language="Json"}}
... ... @@ -871,12 +871,10 @@
871 871   }
872 872  {{/code}}
873 873  
874 -While making first search request, paging id should be empty,  "pageNumber":  and  "pageRowCount":10 means that, in response there will be returned maximum 10 packages per page.
875 875  
876 -
877 877  ==== Request with caching ====
878 878  
879 -after receiving response from first search request, in the end we can see pagingId- number, wchich we can use for caching, and (pageinatoin) for switch pagenumbers, and displaying results as we whant. For cleaning cache, it's important to make new request without cllear pagingID, like this  "pagingId": "",
828 +as we receive response, in the end we can see pagingId- number, chich we can use for caching, and then just switch pagenumbers. for cleaning cache, it's important to make new request without pagingID
880 880  
881 881  {{code language="Json"}}
882 882   {
... ... @@ -925,21 +925,22 @@
925 925  {{/code}}
926 926  
927 927  
877 +
928 928  == Important ==
929 929  
930 930  {{error}}
931 -=== Implementing Authorization in Subsequent Requests ===
881 +It's Important to in every other request header, put Auth token
932 932  
933 -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:
883 +**Key **- Authorization
934 934  
935 -* **Header Key:** Authorization
936 -* **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.
885 +**Value **- Bearer Token what is given in this response.
937 937  
938 -Additionally, to ensure your requests are properly formatted and recognized, include the following headers:
939 939  
940 -* **Content-Type:** Specify this header as application/json to indicate the format of the request body.
941 -* **Header Key:** X-nugios-timezone
942 -* **Header Value:** 240 - Adjust this value to match your local timezone offset in minutes.
888 +**also note in headers that:**
943 943  
944 -Incorporating these headers with their respective values is essential for the successful processing of your API requests.
890 +Content-Type - application/json
891 +
892 +**Key - **X-nugios-timezone
893 +
894 +**Value **- 240
945 945  {{/error}}