Skip to Content

Changes for page 1. SearchTourPackages

Last modified by Giorgi Mdivnishvili on 2025/02/12 15:25
From version 32.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" %)
... ... @@ -795,6 +795,7 @@
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  
799 +
798 798  (% class="wikigeneratedid" %)
799 799  **Response Parameters**
800 800  
... ... @@ -867,7 +867,7 @@
867 867  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:
868 868  
869 869  
870 -==== First request ====
872 +==== first request ====
871 871  
872 872  {{code language="Json"}}
873 873   {
... ... @@ -877,12 +877,10 @@
877 877   }
878 878  {{/code}}
879 879  
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.
881 881  
882 -
883 883  ==== Request with caching ====
884 884  
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": "",
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
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