Changes for page 1. Authorization
Last modified by Giorgi Mdivnishvili on 2024/04/26 15:59
From version 20.1
edited by Giorgi Mdivnishvili
on 2023/12/26 15:04
on 2023/12/26 15:04
Change comment:
There is no comment for this version
To version 35.1
edited by Giorgi Mdivnishvili
on 2024/04/26 15:59
on 2024/04/26 15:59
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,29 +1,22 @@ 1 1 (% data-xwiki-non-generated-content="java.util.List" %) 2 2 ((( 3 - "data-xwiki-parameter-name="title" class="xwiki-metadata-container">**Contents**3 + 4 4 ))) 5 5 6 -(% data-xwiki-non-generated-content="java.util.List" %) 7 -((( 8 -" class="xwiki-metadata-container"> 9 - 10 -{{toc/}} 11 -))) 12 - 13 13 {{box cssClass="floatinginfobox" title="**Contents**"}} 14 14 {{toc/}} 15 15 {{/box}} 16 16 17 -= MethodDescription =10 += Authorization: Starting Your Integration = 18 18 19 -The i nitialmethod of the integrationprocessis authorization.Youwill beprovidedwithausername and password to generatethe access token thatyouwillneedtopass in allthefollowingmethods.12 +The first step in integrating with our API is the authorization process. As a developer, you'll be assigned a unique username and password. These credentials are essential for generating the access token, a critical component that must be included in the headers of all subsequent API requests. This token validates your requests and grants you access to the full suite of our services. 20 20 21 21 22 -== Request URL - [ GET] ==15 +== Request URL - [POST] == 23 23 24 24 (% class="box infomessage" %) 25 25 ((( 26 -https:~/~/on line-api.kazunion.com/api/Auth/Auth19 +[[https:~~/~~/integration.kazunion.com/api/Auth/Auth>>https://integration.kazunion.com/api/Auth/Auth]] 27 27 ))) 28 28 29 29 ... ... @@ -49,54 +49,99 @@ 49 49 50 50 {{code language="Json"}} 51 51 { 52 - "accessToken": "string" 45 + "accessToken": "string", 46 + "refreshToken": "string", 47 + "passwordExpired": true 53 53 } 54 54 {{/code}} 55 55 56 56 52 +expiration time 30 days for both tokens: 53 + 54 +accessToken - 43200 min 55 + 56 +refreshToken - 2591968 sec 57 + 58 + 57 57 === Schema === 58 58 59 59 (% data-xwiki-non-generated-content="java.util.List" %) 60 60 ((( 61 -" class="xwiki-metadata-container">AuthRequest{ 63 + 64 +))) 62 62 63 -|login|string 66 +{{success}} 67 +AuthResponse{ 68 + 69 +|accessToken|string 64 64 nullable: true 65 -| password|string71 +|refreshToken|string 66 66 nullable: true 73 +|passwordExpired|boolean 67 67 68 68 } 76 +{{/success}} 77 + 78 + 79 + 80 + 81 += RefreshToken = 82 + 83 + 84 +To retrieve an existing accesstoken , you can make a request for the given endpoint below and pass in the body refreshToken, after that you will receive an accessToken. You can use this method at your discretion. 85 + 86 + 87 +== Request URL - [POST] == 88 + 89 +(% class="box infomessage" %) 90 +((( 91 +[[https:~~/~~/integration.kazunion.com/api/Auth/RefreshToken>>https://integration.kazunion.com/api/Auth/RefreshToken]] 69 69 ))) 70 70 71 -{{success}} 72 -AuthRequest{ 73 73 74 -|login|string 75 -nullable: true 76 -|password|string 77 -nullable: true 95 +== Request Parameters == 78 78 97 +(% class="box" %) 98 +((( 99 +none 100 +))) 101 + 102 + 103 +== (% id="cke_bm_5539S" style="display:none" %) (%%)Request Body example == 104 + 105 +{{code language="Json"}} 106 +{ 107 + "refreshToken": "string" 79 79 } 80 -{{/ success}}109 +{{/code}} 81 81 82 82 83 -== Important==112 +== (% id="cke_bm_11208S" style="display:none" %) (%%)Response Body == 84 84 85 -{{error}} 86 -It's Important to in every other request header, put Auth token 114 +{{code language="Json"}} 115 +{ 116 + "accessToken": "string", 117 + "refreshToken": "string", 118 + "passwordExpired": true 119 +} 120 +{{/code}} 87 87 88 -**Key **- Authorization 89 89 90 - **Value**- Bearer Token whatis giveninthisresponse.123 +== Important == 91 91 125 +{{error}} 126 +=== Implementing Authorization in Subsequent Requests === 92 92 93 - **also note in headers that:**128 +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: 94 94 95 -Content-Type - application/json 130 +* **Header Key:** Authorization 131 +* **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. 96 96 97 - **Key-**X-nugios-timezone133 +Additionally, to ensure your requests are properly formatted and recognized, include the following headers: 98 98 99 -**Value **- 240 100 -{{/error}} 135 +* **Content-Type:** Specify this header as application/json to indicate the format of the request body. 136 +* **Header Key:** X-nugios-timezone 137 +* **Header Value:** 240 - Adjust this value to match your local timezone offset in minutes. 101 101 102 - 139 +Incorporating these headers with their respective values is essential for the successful processing of your API requests. 140 +{{/error}}