Changes for page 1. SearchTourPackages

Summary

• Page properties (1 modified, 0 added, 0 removed)

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}}
...	...	@@ -760,7 +760,6 @@
760	760
761	761	== Definitions ==
762	762
763		-
764	764	**Request Parameters **
765	765
766	766	(% class="table-bordered" %)
...	...	@@ -868,7 +868,7 @@
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:
869	869
870	870
871		-==== first request ====
	891	+==== First request ====
872	872
873	873	{{code language="Json"}}
874	874	{
...	...	@@ -878,10 +878,12 @@
878	878	}
879	879	{{/code}}
880	880
	901	+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.
881	881
	903	+
882	882	==== Request with caching ====
883	883
884		-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
	906	+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": "",
885	885
886	886	{{code language="Json"}}
887	887	{
...	...	@@ -892,7 +892,7 @@
892	892	{{/code}}
893	893
894	894
895		-=== search parameter options ===
	917	+=== Search parameter options ===
896	896
897	897	in the request body it's available to filter search results with parameters. parameter examples:
898	898
...	...	@@ -934,18 +934,18 @@
934	934	== Important ==
935	935
936	936	{{error}}
937		-It's Important to in every other request header, put Auth token
	959	+=== Implementing Authorization in Subsequent Requests ===
938	938
939		-**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:
940	940
941		-**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.
942	942
	966	+Additionally, to ensure your requests are properly formatted and recognized, include the following headers:
943	943
944		-**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.
945	945
946		-Content-Type - application/json
947		-
948		-**Key - **X-nugios-timezone
949		-
950		-**Value **- 240
	972	+Incorporating these headers with their respective values is essential for the successful processing of your API requests.
951	951	{{/error}}