Skip to Content

Changes for page 1. SearchTourPackages

Last modified by Giorgi Mdivnishvili on 2025/02/12 15:25
From version 35.1
edited by Giorgi Mdivnishvili
on 2024/04/11 16:44
Change comment: There is no comment for this version
To version 33.1
edited by Giorgi Mdivnishvili
on 2024/04/11 11:46
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -936,18 +936,18 @@
936 936  == Important ==
937 937  
938 938  {{error}}
939 -=== Implementing Authorization in Subsequent Requests ===
939 +It's Important to in every other request header, put Auth token
940 940  
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:
941 +**Key **- Authorization
942 942  
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.
943 +**Value **- Bearer Token what is given in this response.
945 945  
946 -Additionally, to ensure your requests are properly formatted and recognized, include the following headers:
947 947  
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.
946 +**also note in headers that:**
951 951  
952 -Incorporating these headers with their respective values is essential for the successful processing of your API requests.
948 +Content-Type - application/json
949 +
950 +**Key - **X-nugios-timezone
951 +
952 +**Value **- 240
953 953  {{/error}}