Wiki source code of 1. Authorization
Version 31.2 by Giorgi Mdivnishvili on 2024/04/11 15:37
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
19.1 | 1 | (% data-xwiki-non-generated-content="java.util.List" %) |
| 2 | ((( | ||
| |
21.1 | 3 | |
| |
19.1 | 4 | ))) |
| 5 | |||
| |
1.1 | 6 | {{box cssClass="floatinginfobox" title="**Contents**"}} |
| 7 | {{toc/}} | ||
| 8 | {{/box}} | ||
| 9 | |||
| |
30.1 | 10 | = Authorization: Starting Your Integration = |
| |
1.1 | 11 | |
| |
28.1 | 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. |
| 13 | |||
| 14 | |||
| |
22.1 | 15 | == Request URL - [POST] == |
| |
1.1 | 16 | |
| |
6.1 | 17 | (% class="box infomessage" %) |
| 18 | ((( | ||
| |
25.1 | 19 | [[https:~~/~~/integration.kazunion.com/api/Auth/Auth>>https://integration.kazunion.com/api/Auth/Auth]] |
| |
6.1 | 20 | ))) |
| |
1.1 | 21 | |
| |
6.1 | 22 | |
| |
1.1 | 23 | == Request Parameters == |
| 24 | |||
| |
6.1 | 25 | (% class="box" %) |
| 26 | ((( | ||
| |
1.1 | 27 | none |
| |
6.1 | 28 | ))) |
| |
1.1 | 29 | |
| |
6.1 | 30 | |
| |
1.1 | 31 | == Request Body == |
| 32 | |||
| 33 | {{code language="Json"}} | ||
| 34 | { | ||
| 35 | "login": "string", | ||
| 36 | "password": "string" | ||
| 37 | } | ||
| 38 | {{/code}} | ||
| 39 | |||
| |
9.1 | 40 | |
| |
1.1 | 41 | == Response Body == |
| 42 | |||
| 43 | {{code language="Json"}} | ||
| 44 | { | ||
| |
30.2 | 45 | "accessToken": "string", |
| 46 | "refreshToken": "string", | ||
| 47 | "passwordExpired": true | ||
| |
1.1 | 48 | } |
| 49 | {{/code}} | ||
| 50 | |||
| |
12.1 | 51 | |
| |
27.1 | 52 | |
| |
1.1 | 53 | === Schema === |
| 54 | |||
| |
19.1 | 55 | (% data-xwiki-non-generated-content="java.util.List" %) |
| 56 | ((( | ||
| |
26.1 | 57 | |
| |
19.1 | 58 | ))) |
| 59 | |||
| |
11.1 | 60 | {{success}} |
| |
30.2 | 61 | AuthResponse{ |
| |
11.1 | 62 | |
| |
30.2 | 63 | |accessToken|string |
| |
11.1 | 64 | nullable: true |
| |
30.2 | 65 | |refreshToken|string |
| |
11.1 | 66 | nullable: true |
| |
30.2 | 67 | |passwordExpired|boolean |
| |
11.1 | 68 | |
| |
3.1 | 69 | } |
| |
11.1 | 70 | {{/success}} |
| 71 | |||
| |
16.1 | 72 | |
| 73 | == Important == | ||
| 74 | |||
| 75 | {{error}} | ||
| |
31.1 | 76 | === Implementing Authorization in Subsequent Requests === |
| |
16.1 | 77 | |
| |
31.1 | 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: |
| |
16.1 | 79 | |
| |
31.1 | 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. | ||
| |
16.1 | 82 | |
| |
31.1 | 83 | Additionally, to ensure your requests are properly formatted and recognized, include the following headers: |
| |
16.1 | 84 | |
| |
31.1 | 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. | ||
| |
16.1 | 88 | |
| |
31.1 | 89 | Incorporating these headers with their respective values is essential for the successful processing of your API requests. |
| |
16.1 | 90 | {{/error}} |