Skip to Content
Last modified by Giorgi Mdivnishvili on 2024/07/11 12:45
From version 9.1
edited by Giorgi Mdivnishvili
on 2024/04/11 11:27
Change comment: There is no comment for this version
To version 11.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
... ... @@ -46,7 +46,7 @@
46 46  }
47 47  {{/code}}
48 48  
49 -== Request example 2Adults 2Child ==
49 +== Request example for 2Adults 2Child ==
50 50  
51 51  {{code language="Json"}}
52 52  {
... ... @@ -840,6 +840,8 @@
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 +
843 843  ==== first request ====
844 844  
845 845  {{code language="Json"}}
... ... @@ -850,10 +850,12 @@
850 850   }
851 851  {{/code}}
852 852  
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.
853 853  
857 +
854 854  ==== Request with caching ====
855 855  
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
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": "",
857 857  
858 858  {{code language="Json"}}
859 859   {
... ... @@ -906,18 +906,18 @@
906 906  == Important ==
907 907  
908 908  {{error}}
909 -It's Important to in every other request header, put Auth token
913 +=== Implementing Authorization in Subsequent Requests ===
910 910  
911 -**Key **- Authorization
915 +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:
912 912  
913 -**Value **- Bearer Token what is given in this response.
917 +* **Header Key:** Authorization
918 +* **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.
914 914  
920 +Additionally, to ensure your requests are properly formatted and recognized, include the following headers:
915 915  
916 -**also note in headers that:**
922 +* **Content-Type:** Specify this header as application/json to indicate the format of the request body.
923 +* **Header Key:** X-nugios-timezone
924 +* **Header Value:** 240 - Adjust this value to match your local timezone offset in minutes.
917 917  
918 -Content-Type - application/json
919 -
920 -**Key - **X-nugios-timezone
921 -
922 -**Value **- 240
926 +Incorporating these headers with their respective values is essential for the successful processing of your API requests.
923 923  {{/error}}