Skip to Content

Changes for page 1. SearchTourPackages

Last modified by Giorgi Mdivnishvili on 2025/02/12 15:25
From version 30.1
edited by Giorgi Mdivnishvili
on 2024/04/11 11:45
Change comment: There is no comment for this version
To version 26.1
edited by Giorgi Mdivnishvili
on 2024/04/10 12:01
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -757,8 +757,10 @@
757 757  }
758 758  {{/success}}
759 759  
760 +
760 760  == Definitions ==
761 761  
763 +
762 762  **Request Parameters **
763 763  
764 764  (% class="table-bordered" %)
... ... @@ -861,8 +861,6 @@
861 861  |totalCount|integer|The total count of packages.
862 862  |error|boolean|Indicates whether there was an error.
863 863  
864 -=== ===
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:
... ... @@ -878,12 +878,10 @@
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.
882 882  
883 -
884 884  ==== Request with caching ====
885 885  
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": "",
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
887 887  
888 888  {{code language="Json"}}
889 889   {
... ... @@ -894,7 +894,7 @@
894 894  {{/code}}
895 895  
896 896  
897 -=== Search parameter options ===
895 +=== search parameter options ===
898 898  
899 899  in the request body it's available to filter search results with parameters. parameter examples:
900 900