Skip to Content
Last modified by Giorgi Mdivnishvili on 2025/10/22 13:39
From version 10.1
edited by Giorgi Mdivnishvili
on 2024/04/11 11:32
Change comment: There is no comment for this version
To version 9.1
edited by Giorgi Mdivnishvili
on 2024/04/11 11:27
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -46,7 +46,7 @@
46 46  }
47 47  {{/code}}
48 48  
49 -== Request example for 2Adults 2Child ==
49 +== Request example 2Adults 2Child ==
50 50  
51 51  {{code language="Json"}}
52 52  {
... ... @@ -840,8 +840,6 @@
840 840  |totalCount|Number|The total count of packages. This is the total number of packages in all pages of results.
841 841  |error|Boolean|A boolean indicating whether there was an error. If true, it means that there was an error in retrieving the packages.
842 842  
843 -==== ====
844 -
845 845  ==== first request ====
846 846  
847 847  {{code language="Json"}}
... ... @@ -852,12 +852,10 @@
852 852   }
853 853  {{/code}}
854 854  
855 -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.
856 856  
857 -
858 858  ==== Request with caching ====
859 859  
860 -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": "",
856 +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
861 861  
862 862  {{code language="Json"}}
863 863   {