Changes for page 1. SearchTourPackages
Last modified by Giorgi Mdivnishvili on 2025/02/12 15:25
From version 29.1
edited by Giorgi Mdivnishvili
on 2024/04/11 11:35
on 2024/04/11 11:35
Change comment:
There is no comment for this version
To version 35.1
edited by Giorgi Mdivnishvili
on 2024/04/11 16:44
on 2024/04/11 16:44
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -760,7 +760,6 @@ 760 760 761 761 == Definitions == 762 762 763 - 764 764 **Request Parameters ** 765 765 766 766 (% class="table-bordered" %) ... ... @@ -863,7 +863,6 @@ 863 863 |totalCount|integer|The total count of packages. 864 864 |error|boolean|Indicates whether there was an error. 865 865 866 -=== === 867 867 868 868 === Paging and Caching === 869 869 ... ... @@ -870,7 +870,7 @@ 870 870 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: 871 871 872 872 873 -==== first request ====871 +==== First request ==== 874 874 875 875 {{code language="Json"}} 876 876 { ... ... @@ -938,18 +938,18 @@ 938 938 == Important == 939 939 940 940 {{error}} 941 - It'sImportant to in every otherrequestheader, put Auth token939 +=== Implementing Authorization in Subsequent Requests === 942 942 943 - **Key**-Authorization941 +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: 944 944 945 -**Value **- Bearer Token what is given in this response. 943 +* **Header Key:** Authorization 944 +* **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. 946 946 946 +Additionally, to ensure your requests are properly formatted and recognized, include the following headers: 947 947 948 -**also note in headers that:** 948 +* **Content-Type:** Specify this header as application/json to indicate the format of the request body. 949 +* **Header Key:** X-nugios-timezone 950 +* **Header Value:** 240 - Adjust this value to match your local timezone offset in minutes. 949 949 950 -Content-Type - application/json 951 - 952 -**Key - **X-nugios-timezone 953 - 954 -**Value **- 240 952 +Incorporating these headers with their respective values is essential for the successful processing of your API requests. 955 955 {{/error}}