Changes for page 1. SearchTourPackages

Summary

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

Details

Page properties

Content

...	...	@@ -760,7 +760,7 @@
760	760
761	761	== Definitions ==
762	762
763		-Request Parameters
	763	+**Request Parameters **
764	764
765	765	(% class="table-bordered" %)
766	766	|=Field|=Type|=Description
...	...	@@ -795,13 +795,9 @@
795	795	|pageNumber|integer|The page number for paginated results.
796	796	|pageRowCount|integer|The number of rows per page for paginated results.
797	797
798		-
799	799	(% class="wikigeneratedid" %)
800		-Response Parameters
	799	+**Response Parameters**
801	801
802		-
803		-
804		-
805	805	(% class="table-bordered" %)
806	806	|=Field|=Type|=Description
807	807	|packages|array|An array of packages available. Each package contains:
...	...	@@ -871,7 +871,7 @@
871	871	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:
872	872
873	873
874		-==== first request ====
	870	+==== First request ====
875	875
876	876	{{code language="Json"}}
877	877	{
...	...	@@ -881,10 +881,12 @@
881	881	}
882	882	{{/code}}
883	883
	880	+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.
884	884
	882	+
885	885	==== Request with caching ====
886	886
887		-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
	885	+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": "",
888	888
889	889	{{code language="Json"}}
890	890	{
...	...	@@ -895,7 +895,7 @@
895	895	{{/code}}
896	896
897	897
898		-=== search parameter options ===
	896	+=== Search parameter options ===
899	899
900	900	in the request body it's available to filter search results with parameters. parameter examples:
901	901
...	...	@@ -937,18 +937,18 @@
937	937	== Important ==
938	938
939	939	{{error}}
940		-It's Important to in every other request header, put Auth token
	938	+=== Implementing Authorization in Subsequent Requests ===
941	941
942		-**Key **- Authorization
	940	+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:
943	943
944		-**Value **- Bearer Token what is given in this response.
	942	+* **Header Key:** Authorization
	943	+* **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.
945	945
	945	+Additionally, to ensure your requests are properly formatted and recognized, include the following headers:
946	946
947		-**also note in headers that:**
	947	+* **Content-Type:** Specify this header as application/json to indicate the format of the request body.
	948	+* **Header Key:** X-nugios-timezone
	949	+* **Header Value:** 240 - Adjust this value to match your local timezone offset in minutes.
948	948
949		-Content-Type - application/json
950		-
951		-**Key - **X-nugios-timezone
952		-
953		-**Value **- 240
	951	+Incorporating these headers with their respective values is essential for the successful processing of your API requests.
954	954	{{/error}}