Skip to Content

Changes for page 1. SearchTourPackages

Last modified by Giorgi Mdivnishvili on 2025/02/12 15:25
From version 25.1
edited by Giorgi Mdivnishvili
on 2024/04/10 11:12
Change comment: There is no comment for this version
To version 36.1
edited by Giorgi Mdivnishvili
on 2024/04/11 17:14
Change comment: There is no comment for this version

Summary

Details

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