Skip to Content
Last modified by Giorgi Mdivnishvili on 2025/10/22 13:39
From version 12.1
edited by Giorgi Mdivnishvili
on 2024/04/11 17:31
Change comment: There is no comment for this version
To version 10.1
edited by Giorgi Mdivnishvili
on 2024/04/11 11:32
Change comment: There is no comment for this version

Summary

Details

Page properties
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}}
... ... @@ -931,18 +931,18 @@
931 931  == Important ==
932 932  
933 933  {{error}}
934 -=== Implementing Authorization in Subsequent Requests ===
913 +It's Important to in every other request header, put Auth token
935 935  
936 -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:
915 +**Key **- Authorization
937 937  
938 -* **Header Key:** Authorization
939 -* **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.
917 +**Value **- Bearer Token what is given in this response.
940 940  
941 -Additionally, to ensure your requests are properly formatted and recognized, include the following headers:
942 942  
943 -* **Content-Type:** Specify this header as application/json to indicate the format of the request body.
944 -* **Header Key:** X-nugios-timezone
945 -* **Header Value:** 240 - Adjust this value to match your local timezone offset in minutes.
920 +**also note in headers that:**
946 946  
947 -Incorporating these headers with their respective values is essential for the successful processing of your API requests.
922 +Content-Type - application/json
923 +
924 +**Key - **X-nugios-timezone
925 +
926 +**Value **- 240
948 948  {{/error}}