Skip to Content
Last modified by Giorgi Mdivnishvili on 2025/10/22 13:39
From version 11.1
edited by Giorgi Mdivnishvili
on 2024/04/11 16:44
Change comment: There is no comment for this version
To version 8.1
edited by Giorgi Mdivnishvili
on 2024/04/11 11:21
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  {
... ... @@ -67,7 +67,7 @@
67 67   "checkInAndCheckOutDaysCount": 7,
68 68   "directFlightsOnly": true,
69 69   "searchCurrency": "USD",
70 -
70 +
71 71   "pagingId": "",
72 72   "pageNumber": 1,
73 73   "pageRowCount":5
... ... @@ -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   {
... ... @@ -910,18 +910,18 @@
910 910  == Important ==
911 911  
912 912  {{error}}
913 -=== Implementing Authorization in Subsequent Requests ===
909 +It's Important to in every other request header, put Auth token
914 914  
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:
911 +**Key **- Authorization
916 916  
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.
913 +**Value **- Bearer Token what is given in this response.
919 919  
920 -Additionally, to ensure your requests are properly formatted and recognized, include the following headers:
921 921  
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.
916 +**also note in headers that:**
925 925  
926 -Incorporating these headers with their respective values is essential for the successful processing of your API requests.
918 +Content-Type - application/json
919 +
920 +**Key - **X-nugios-timezone
921 +
922 +**Value **- 240
927 927  {{/error}}