Skip to Content

Changes for page 1. SearchTourPackages

Last modified by Giorgi Mdivnishvili on 2025/02/12 15:25
From version 27.1
edited by Giorgi Mdivnishvili
on 2024/04/11 11:34
Change comment: There is no comment for this version
To version 36.1
edited by Giorgi Mdivnishvili
on 2024/04/11 17:14
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" %)
... ... @@ -868,7 +868,7 @@
868 868  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:
869 869  
870 870  
871 -==== first request ====
870 +==== First request ====
872 872  
873 873  {{code language="Json"}}
874 874   {
... ... @@ -894,7 +894,7 @@
894 894  {{/code}}
895 895  
896 896  
897 -=== search parameter options ===
896 +=== Search parameter options ===
898 898  
899 899  in the request body it's available to filter search results with parameters. parameter examples:
900 900  
... ... @@ -936,18 +936,18 @@
936 936  == Important ==
937 937  
938 938  {{error}}
939 -It's Important to in every other request header, put Auth token
938 +=== Implementing Authorization in Subsequent Requests ===
940 940  
941 -**Key **- Authorization
940 +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:
942 942  
943 -**Value **- Bearer Token what is given in this response.
942 +* **Header Key:** Authorization
943 +* **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.
944 944  
945 +Additionally, to ensure your requests are properly formatted and recognized, include the following headers:
945 945  
946 -**also note in headers that:**
947 +* **Content-Type:** Specify this header as application/json to indicate the format of the request body.
948 +* **Header Key:** X-nugios-timezone
949 +* **Header Value:** 240 - Adjust this value to match your local timezone offset in minutes.
947 947  
948 -Content-Type - application/json
949 -
950 -**Key - **X-nugios-timezone
951 -
952 -**Value **- 240
951 +Incorporating these headers with their respective values is essential for the successful processing of your API requests.
953 953  {{/error}}