Skip to Content

Changes for page 1. Authorization

Last modified by Giorgi Mdivnishvili on 2024/04/26 15:59
From version 31.2
edited by Giorgi Mdivnishvili
on 2024/04/11 15:37
Change comment: There is no comment for this version
To version 30.2
edited by Giorgi Mdivnishvili
on 2024/04/11 15:35
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -73,18 +73,18 @@
73 73  == Important ==
74 74  
75 75  {{error}}
76 -=== Implementing Authorization in Subsequent Requests ===
76 +It's Important to in every other request header, put Auth token
77 77  
78 -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:
78 +**Key **- Authorization
79 79  
80 -* **Header Key:** Authorization
81 -* **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.
80 +**Value **- Bearer Token what is given in this response. (Authorization type Bearer Token)
82 82  
83 -Additionally, to ensure your requests are properly formatted and recognized, include the following headers:
84 84  
85 -* **Content-Type:** Specify this header as application/json to indicate the format of the request body.
86 -* **Header Key:** X-nugios-timezone
87 -* **Header Value:** 240 - Adjust this value to match your local timezone offset in minutes.
83 +**also note in headers that:**
88 88  
89 -Incorporating these headers with their respective values is essential for the successful processing of your API requests.
85 +Content-Type - application/json
86 +
87 +**Key - **X-nugios-timezone
88 +
89 +**Value **- 240
90 90  {{/error}}