Web API: Usersettings - Revision history

Ollvihe at 23:35, 17 February 2022

2022-02-17T23:35:24Z

← Older revision		Revision as of 23:35, 17 February 2022
Line 3:		Line 3:
	HTTP request header '''Authorization''' with value '''Bearer <access token>''' needs to be in place to identify the session.		HTTP request header '''Authorization''' with value '''Bearer <access token>''' needs to be in place to identify the session.

	== ~~PUT /api/usersettings/{key}/{value}~~ ==		== Stores single setting ==

	Stores ~~individual~~ user setting to the server.		Stores single user setting to the server.
	<pre>		<pre>
	Url: PUT qprpa/api/usersettings/{key}/{value}		Url: PUT qprpa/api/usersettings/{key}/{value}
Line 14:		Line 14:
	Returns HTTP code 204 (No content).		Returns HTTP code 204 (No content).

	== ~~POST qprpa/api/usersettings/~~ ==		== Store multiple settings ==

	Stores multiple user settings to the server at the same time. Possible existing settings in the server that are not mentioned in the request, are not removed.		Stores multiple user settings to the server at the same time. Possible existing settings in the server that are not mentioned in the request, are not removed.
	<pre>		<pre>
	Url: POST /api/usersettings/		Url: POST qprpa//api/usersettings/
	</pre>		</pre>

Ollvihe at 23:34, 17 February 2022

2022-02-17T23:34:27Z

← Older revision		Revision as of 23:34, 17 February 2022
Line 14:		Line 14:
	Returns HTTP code 204 (No content).		Returns HTTP code 204 (No content).

	== POST /api/usersettings/ ==		== POST qprpa/api/usersettings/ ==

	Stores multiple user settings to the server at the same time. Possible existing settings in the server that are not mentioned in the request, are not removed.		Stores multiple user settings to the server at the same time. Possible existing settings in the server that are not mentioned in the request, are not removed.

Ollvihe at 10:05, 16 February 2022

2022-02-16T10:05:18Z

← Older revision		Revision as of 10:05, 16 February 2022
Line 7:		Line 7:
	Stores individual user setting to the server.		Stores individual user setting to the server.
	<pre>		<pre>
	Url: PUT /api/usersettings/{key}/{value}		Url: PUT qprpa/api/usersettings/{key}/{value}
	</pre>		</pre>

Ollvihe at 13:32, 4 October 2021

2021-10-04T13:32:32Z

← Older revision		Revision as of 13:32, 4 October 2021
Line 5:		Line 5:
	== PUT /api/usersettings/{key}/{value} ==		== PUT /api/usersettings/{key}/{value} ==

	Stores individual setting to the server.		Stores individual user setting to the server.
	<pre>		<pre>
	Url: PUT /api/usersettings/{key}/{value}		Url: PUT /api/usersettings/{key}/{value}
Line 16:		Line 16:
	== POST /api/usersettings/ ==		== POST /api/usersettings/ ==

	Stores multiple settings to the server. ~~Settings~~ that are not mentioned, are not removed.		Stores multiple user settings to the server at the same time. Possible existing settings in the server that are not mentioned in the request, are not removed.
	<pre>		<pre>
	Url: POST /api/usersettings/		Url: POST /api/usersettings/
	</pre>		</pre>

	The request body contains an object that has ~~properties~~ for all the stored ~~settings~~.		The request body contains an object that has fields for all the settings to be stored.

	Returns HTTP code 204 (No content).		Returns HTTP code 204 (No content).

	[[Category: QPR ProcessAnalyzer]]		[[Category: QPR ProcessAnalyzer]]

Ollvihe at 14:12, 20 September 2021

2021-09-20T14:12:41Z

← Older revision		Revision as of 14:12, 20 September 2021
Line 1:		Line 1:
	The '''~~Usersettings~~''' saves user specific settings to server. The PUT version is used to store individual setting and the POST version to store multiple settings.		The '''usersettings''' operation saves user specific settings to server. The PUT version is used to store an individual setting and the POST version to store multiple settings.

	HTTP request header '''Authorization''' with value '''Bearer <access token>''' needs to be in place to identify the session.		HTTP request header '''Authorization''' with value '''Bearer <access token>''' needs to be in place to identify the session.

	== PUT /api/usersettings/{key}/{value} ==		== PUT /api/usersettings/{key}/{value} ==

	Stores individual setting to the server.		Stores individual setting to the server.

	<pre>		<pre>
	Url: PUT /api/usersettings/{key}/{value}		Url: PUT /api/usersettings/{key}/{value}
Line 15:		Line 15:

	== POST /api/usersettings/ ==		== POST /api/usersettings/ ==
	~~Stores multiple settings to the server.~~

			Stores multiple settings to the server. Settings that are not mentioned, are not removed.
	<pre>		<pre>
	Url: POST /api/usersettings/		Url: POST /api/usersettings/

Ollvihe at 14:09, 20 September 2021

2021-09-20T14:09:48Z

← Older revision		Revision as of 14:09, 20 September 2021
Line 1:		Line 1:
	The '''Usersettings''' saves user specific settings to server.		The '''Usersettings''' saves user specific settings to server. The PUT version is used to store individual setting and the POST version to store multiple settings.

	HTTP request header '''Authorization''' with value '''Bearer <access token>''' needs to be in place to identify the session.		HTTP request header '''Authorization''' with value '''Bearer <access token>''' needs to be in place to identify the session.

			== PUT /api/usersettings/{key}/{value} ==
			Stores individual setting to the server.

	<pre>		<pre>
Line 8:		Line 11:

	The '''key''' is the setting name and '''value''' is the setting value.		The '''key''' is the setting name and '''value''' is the setting value.

			Returns HTTP code 204 (No content).

			== POST /api/usersettings/ ==
			Stores multiple settings to the server.

			<pre>
			Url: POST /api/usersettings/
			</pre>

			The request body contains an object that has properties for all the stored settings.

	Returns HTTP code 204 (No content).		Returns HTTP code 204 (No content).

	[[Category: QPR ProcessAnalyzer]]		[[Category: QPR ProcessAnalyzer]]

Ollvihe at 13:52, 28 May 2020

2020-05-28T13:52:28Z

← Older revision		Revision as of 13:52, 28 May 2020
Line 10:		Line 10:

	Returns HTTP code 204 (No content).		Returns HTTP code 204 (No content).

			[[Category: QPR ProcessAnalyzer]]

Ollvihe: Created page with "The '''Usersettings''' saves user specific settings to server. HTTP request header '''Authorization''' with value '''Bearer ''' needs to be in place to identify..."

2020-05-28T10:06:13Z

Created page with "The '''Usersettings''' saves user specific settings to server. HTTP request header '''Authorization''' with value '''Bearer <access token>''' needs to be in place to identify..."

New page

The '''Usersettings''' saves user specific settings to server.

HTTP request header '''Authorization''' with value '''Bearer <access token>''' needs to be in place to identify the session.

<pre>
Url: PUT /api/usersettings/{key}/{value}
</pre>

The '''key''' is the setting name and '''value''' is the setting value.

Returns HTTP code 204 (No content).