Changes for page 1. Authorization

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -1,17 +1,22 @@
	1	+(% data-xwiki-non-generated-content="java.util.List" %)
	2	+(((
	3	+
	4	+)))
	5	+
1	1	{{box cssClass="floatinginfobox" title="**Contents**"}}
2	2	{{toc/}}
3	3	{{/box}}
4	4
5		-= Method Description =
	10	+= Authorization: Starting Your Integration =
6	6
7		-The initial method of the integration process is authorization. You will be provided with a  unique user username and password to generate the access token that you will need to pass in all the following methods.
	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.
8	8
9	9
10		-== Request URL - [GET] ==
	15	+== Request URL - [POST] ==
11	11
12	12	(% class="box infomessage" %)
13	13	(((
14		-https:~/~/online-api.kazunion.com/api/Auth/Auth
	19	+[[https:~~/~~/integration.kazunion.com/api/Auth/Auth>>https://integration.kazunion.com/api/Auth/Auth]]
15	15	)))
16	16
17	17
...	...	@@ -37,20 +37,35 @@
37	37
38	38	{{code language="Json"}}
39	39	{
40		- "accessToken": "string"
	45	+ "accessToken": "string",
	46	+ "refreshToken": "string",
	47	+ "passwordExpired": true
41	41	}
42	42	{{/code}}
43	43
44	44
	52	+expiration time 30 days for both tokens:
	53	+
	54	+accessToken - 43200 min
	55	+
	56	+refreshToken - 2591968 sec
	57	+
	58	+
45	45	=== Schema ===
46	46
	61	+(% data-xwiki-non-generated-content="java.util.List" %)
	62	+(((
	63	+
	64	+)))
	65	+
47	47	{{success}}
48		-AuthRequest{
	67	+AuthResponse{
49	49
50		-|login|string
	69	+|accessToken|string
51	51	nullable: true
52		-|password|string
	71	+|refreshToken|string
53	53	nullable: true
	73	+|passwordExpired|boolean
54	54
55	55	}
56	56	{{/success}}
...	...	@@ -59,20 +59,18 @@
59	59	== Important ==
60	60
61	61	{{error}}
62		-It's Important to in every other request header, put Auth token
	82	+=== Implementing Authorization in Subsequent Requests ===
63	63
64		-**Key **- Authorization
	84	+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:
65	65
66		-**Value **- Bearer Token what is given in this response.
	86	+* **Header Key:** Authorization
	87	+* **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.
67	67
	89	+Additionally, to ensure your requests are properly formatted and recognized, include the following headers:
68	68
69		-**also note in headers that:**
	91	+* **Content-Type:** Specify this header as application/json to indicate the format of the request body.
	92	+* **Header Key:** X-nugios-timezone
	93	+* **Header Value:** 240 - Adjust this value to match your local timezone offset in minutes.
70	70
71		-Content-Type - application/json
72		-
73		-**Key - **X-nugios-timezone
74		-
75		-**Value **- 240
	95	+Incorporating these headers with their respective values is essential for the successful processing of your API requests.
76	76	{{/error}}
77		-
78		-