Skip to Content
Last modified by Giorgi Mdivnishvili on 2024/07/11 12:45
From version 7.1
edited by Giorgi Mdivnishvili
on 2024/04/11 11:05
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,35 @@
46 46  }
47 47  {{/code}}
48 48  
49 +== Request example for 2Adults 2Child ==
49 49  
51 +{{code language="Json"}}
52 +{
53 + "departureCountryCode": "KZ",
54 + "departureCityUID": "f0ba6324-f337-405c-8cc7-23d62cf664e8",
55 + "arrivalCountryCode": "AE",
56 + "adults": 2,
57 + "children": 2,
58 + "childrenAges": [
59 + 4,
60 + 8
61 + ],
62 + "departureDate": "2024-05-26T00:00:00",
63 + "returnDate": "2024-06-02T00:00:00",
64 + "departureAndReturnDaysCount": 7,
65 + "checkInDate": "2024-05-26T00:00:00",
66 + "checkOutDate": "2024-06-02T00:00:00",
67 + "checkInAndCheckOutDaysCount": 7,
68 + "directFlightsOnly": true,
69 + "searchCurrency": "USD",
70 +
71 + "pagingId": "",
72 + "pageNumber": 1,
73 + "pageRowCount":5
74 +}
75 +{{/code}}
76 +
77 +
50 50  == Response Body ==
51 51  
52 52  {{code language="json"}}
... ... @@ -812,6 +812,8 @@
812 812  |totalCount|Number|The total count of packages. This is the total number of packages in all pages of results.
813 813  |error|Boolean|A boolean indicating whether there was an error. If true, it means that there was an error in retrieving the packages.
814 814  
843 +==== ====
844 +
815 815  ==== first request ====
816 816  
817 817  {{code language="Json"}}
... ... @@ -822,10 +822,12 @@
822 822   }
823 823  {{/code}}
824 824  
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.
825 825  
857 +
826 826  ==== Request with caching ====
827 827  
828 -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": "",
829 829  
830 830  {{code language="Json"}}
831 831   {
... ... @@ -878,18 +878,18 @@
878 878  == Important ==
879 879  
880 880  {{error}}
881 -It's Important to in every other request header, put Auth token
913 +=== Implementing Authorization in Subsequent Requests ===
882 882  
883 -**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:
884 884  
885 -**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.
886 886  
920 +Additionally, to ensure your requests are properly formatted and recognized, include the following headers:
887 887  
888 -**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.
889 889  
890 -Content-Type - application/json
891 -
892 -**Key - **X-nugios-timezone
893 -
894 -**Value **- 240
926 +Incorporating these headers with their respective values is essential for the successful processing of your API requests.
895 895  {{/error}}