Skip to Content
Last modified by Giorgi Mdivnishvili on 2024/07/11 12:45
From version 11.1
edited by Giorgi Mdivnishvili
on 2024/04/11 16:44
Change comment: There is no comment for this version
To version 10.1
edited by Giorgi Mdivnishvili
on 2024/04/11 11:32
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -910,18 +910,18 @@
910 910  == Important ==
911 911  
912 912  {{error}}
913 -=== Implementing Authorization in Subsequent Requests ===
913 +It's Important to in every other request header, put Auth token
914 914  
915 -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:
915 +**Key **- Authorization
916 916  
917 -* **Header Key:** Authorization
918 -* **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.
917 +**Value **- Bearer Token what is given in this response.
919 919  
920 -Additionally, to ensure your requests are properly formatted and recognized, include the following headers:
921 921  
922 -* **Content-Type:** Specify this header as application/json to indicate the format of the request body.
923 -* **Header Key:** X-nugios-timezone
924 -* **Header Value:** 240 - Adjust this value to match your local timezone offset in minutes.
920 +**also note in headers that:**
925 925  
926 -Incorporating these headers with their respective values is essential for the successful processing of your API requests.
922 +Content-Type - application/json
923 +
924 +**Key - **X-nugios-timezone
925 +
926 +**Value **- 240
927 927  {{/error}}