Skip to Content

Changes for page 1. SearchTourPackages

Last modified by Giorgi Mdivnishvili on 2025/02/12 15:25
From version 26.1
edited by Giorgi Mdivnishvili
on 2024/04/10 12:01
Change comment: There is no comment for this version
To version 35.1
edited by Giorgi Mdivnishvili
on 2024/04/11 16:44
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" %)
... ... @@ -863,12 +863,13 @@
863 863  |totalCount|integer|The total count of packages.
864 864  |error|boolean|Indicates whether there was an error.
865 865  
865 +
866 866  === Paging and Caching ===
867 867  
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 ====
871 +==== First request ====
872 872  
873 873  {{code language="Json"}}
874 874   {
... ... @@ -878,10 +878,12 @@
878 878   }
879 879  {{/code}}
880 880  
881 +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  
883 +
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
886 +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 ===
897 +=== 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
939 +=== Implementing Authorization in Subsequent Requests ===
938 938  
939 -**Key **- Authorization
941 +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.
943 +* **Header Key:** Authorization
944 +* **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  
946 +Additionally, to ensure your requests are properly formatted and recognized, include the following headers:
943 943  
944 -**also note in headers that:**
948 +* **Content-Type:** Specify this header as application/json to indicate the format of the request body.
949 +* **Header Key:** X-nugios-timezone
950 +* **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
952 +Incorporating these headers with their respective values is essential for the successful processing of your API requests.
951 951  {{/error}}