Skip to Content

Changes for page 1. SearchTourPackages

Last modified by Giorgi Mdivnishvili on 2025/02/12 15:25
From version 28.1
edited by Giorgi Mdivnishvili
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
Change comment: There is no comment for this version

Summary

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" %)
... ... @@ -796,7 +796,6 @@
796 796  |pageNumber|integer|The page number for paginated results.
797 797  |pageRowCount|integer|The number of rows per page for paginated results.
798 798  
799 -
800 800  (% class="wikigeneratedid" %)
801 801  **Response Parameters**
802 802  
... ... @@ -864,7 +864,6 @@
864 864  |totalCount|integer|The total count of packages.
865 865  |error|boolean|Indicates whether there was an error.
866 866  
867 -=== ===
868 868  
869 869  === Paging and Caching ===
870 870  
... ... @@ -871,7 +871,7 @@
871 871  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:
872 872  
873 873  
874 -==== first request ====
871 +==== First request ====
875 875  
876 876  {{code language="Json"}}
877 877   {
... ... @@ -897,7 +897,7 @@
897 897  {{/code}}
898 898  
899 899  
900 -=== search parameter options ===
897 +=== Search parameter options ===
901 901  
902 902  in the request body it's available to filter search results with parameters. parameter examples:
903 903  
... ... @@ -939,18 +939,18 @@
939 939  == Important ==
940 940  
941 941  {{error}}
942 -It's Important to in every other request header, put Auth token
939 +=== Implementing Authorization in Subsequent Requests ===
943 943  
944 -**Key **- Authorization
941 +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:
945 945  
946 -**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.
947 947  
946 +Additionally, to ensure your requests are properly formatted and recognized, include the following headers:
948 948  
949 -**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.
950 950  
951 -Content-Type - application/json
952 -
953 -**Key - **X-nugios-timezone
954 -
955 -**Value **- 240
952 +Incorporating these headers with their respective values is essential for the successful processing of your API requests.
956 956  {{/error}}