Changes for page 1. SearchTourPackages
Last modified by Giorgi Mdivnishvili on 2025/02/12 15:25
From version 21.1
edited by Giorgi Mdivnishvili
on 2024/01/10 17:51
on 2024/01/10 17:51
Change comment:
There is no comment for this version
To version 15.1
edited by Giorgi Mdivnishvili
on 2023/12/26 14:44
on 2023/12/26 14:44
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -6,15 +6,13 @@ 6 6 7 7 = Method Description = 8 8 9 -To ur packagemean,tour withhotelandflighttogether.Usingthismethod givesdataaboutfullpackage availabilitywith flightand hotel options.9 +The initial method of the integration process is authorization. You will be provided with a test user username and password to generate the access token that you will need to pass in all the following methods. 10 10 11 -It's possible to receive data as current dates, also in date ranges using parameter "stayDays": 0, "stayDaysTo": 0. the maximum difference between the days can be 7. Below you can see examples. 12 12 13 - 14 14 == Endpoint URL - [POST] == 15 15 16 16 {{info}} 17 -[[https:~~/~~/in tegration.kazunion.com/api/TourPackages/SearchTourPackages>>https://integration.kazunion.com/api/TourPackages/SearchTourPackages]]15 +[[https:~~/~~/online-api.kazunion.com/api/TourPackages/SearchTourPackages>>https://online-api.kazunion.com/api/TourPackages/SearchTourPackages]] 18 18 {{/info}} 19 19 20 20 == Request Parameters == ... ... @@ -42,13 +42,13 @@ 42 42 "tag": "string" 43 43 } 44 44 ], 45 - "checkInDate": "2023-12-14", 46 - "checkInDateTo": "2023-12-14", 47 - "checkOutDate": "2023-12-14", 43 + "checkInDate": "2023-12-14T13:43:54.766Z", 44 + "checkInDateTo": "2023-12-14T13:43:54.766Z", 45 + "checkOutDate": "2023-12-14T13:43:54.766Z", 48 48 "stayDays": 0, 49 49 "stayDaysTo": 0, 50 - "departureDate": "2023-12-14", 51 - "returnDate": "2023-12-14", 48 + "departureDate": "2023-12-14T13:43:54.766Z", 49 + "returnDate": "2023-12-14T13:43:54.766Z", 52 52 "airlineCode": "string", 53 53 "ticketType": "string", 54 54 "directFlightsOnly": true, ... ... @@ -763,7 +763,7 @@ 763 763 764 764 === Paging and Caching === 765 765 766 -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:764 +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 767 767 768 768 769 769 ==== first request ==== ... ... @@ -779,8 +779,6 @@ 779 779 780 780 ==== Request with caching ==== 781 781 782 -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 783 - 784 784 {{code language="Json"}} 785 785 { 786 786 "pagingId": "80", ... ... @@ -828,22 +828,4 @@ 828 828 {{/code}} 829 829 830 830 831 - 832 -== Important == 833 - 834 -{{error}} 835 -It's Important to in every other request header, put Auth token 836 - 837 -**Key **- Authorization 838 - 839 -**Value **- Bearer Token what is given in this response. 840 - 841 - 842 -**also note in headers that:** 843 - 844 -Content-Type - application/json 845 - 846 -**Key - **X-nugios-timezone 847 - 848 -**Value **- 240 849 -{{/error}} 827 +