Skip to Content

Changes for page 1. SearchTourPackages

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

Summary

Details

Page properties
Content
... ... @@ -760,6 +760,7 @@
760 760  
761 761  == Definitions ==
762 762  
763 +
763 763  **Request Parameters **
764 764  
765 765  (% class="table-bordered" %)
... ... @@ -863,7 +863,6 @@
863 863  |totalCount|integer|The total count of packages.
864 864  |error|boolean|Indicates whether there was an error.
865 865  
866 -
867 867  === Paging and Caching ===
868 868  
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:
... ... @@ -879,12 +879,10 @@
879 879   }
880 880  {{/code}}
881 881  
882 -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.
883 883  
884 -
885 885  ==== Request with caching ====
886 886  
887 -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 +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
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