AppSuite:HTTP API - Revision history

Khgras: Redirected page to HTTP API

2017-07-05T10:10:33Z

Redirected page to HTTP API

← Older revision		Revision as of 10:10, 5 July 2017
Line 1:		Line 1:
	#REDIRECT [["HTTP_API"]]		#REDIRECT [[HTTP_API]]

Khgras: Redirected page to "HTTP API"

2017-07-05T10:08:19Z

Redirected page to "HTTP API"

← Older revision		Revision as of 10:08, 5 July 2017
Line 1:		Line 1:
	~~The content on this page has moved to https://documentation.open-xchange.com/latest/middleware/http_api.html.~~		#REDIRECT [["HTTP_API"]]

	Note: Open-Xchange is in the process of migrating all its technical documentation to a new and improved documentation system (documentation.open-xchange.com). Please note as the migration takes place more information will be available on the new system and less on this system. Thank you for your understanding during this period of transition.

Khgras at 10:26, 22 May 2017

2017-05-22T10:26:39Z

← Older revision		Revision as of 10:26, 22 May 2017
Line 1:		Line 1:
	The content on this page has moved to https://documentation.open-xchange.com/~~7.8.2~~/middleware/http_api.html.		The content on this page has moved to https://documentation.open-xchange.com/latest/middleware/http_api.html.

	Note: Open-Xchange is in the process of migrating all its technical documentation to a new and improved documentation system (documentation.open-xchange.com). Please note as the migration takes place more information will be available on the new system and less on this system. Thank you for your understanding during this period of transition.		Note: Open-Xchange is in the process of migrating all its technical documentation to a new and improved documentation system (documentation.open-xchange.com). Please note as the migration takes place more information will be available on the new system and less on this system. Thank you for your understanding during this period of transition.

Khgras at 09:30, 12 July 2016

2016-07-12T09:30:46Z

← Older revision		Revision as of 09:30, 12 July 2016
Line 1:		Line 1:
	~~#REDIRECT [~~https://documentation.open-xchange.com/~~latest~~/middleware/http_api.html ~~HTTP API]~~		The content on this page has moved to https://documentation.open-xchange.com/7.8.2/middleware/http_api.html.
	<!-- ~~it's still~~ the ~~same, don't fork it, it~~ will ~~diverge way too fast with fixes still done~~ for ~~OX6 -->~~
			Note: Open-Xchange is in the process of migrating all its technical documentation to a new and improved documentation system (documentation.open-xchange.com). Please note as the migration takes place more information will be available on the new system and less on this system. Thank you for your understanding during this period of transition.

Martin.schneider: Move to https://documentation.open-xchange.com/

2016-06-30T07:49:40Z

Move to https://documentation.open-xchange.com/

← Older revision		Revision as of 07:49, 30 June 2016
Line 1:		Line 1:
	#REDIRECT [[HTTP API]]		#REDIRECT [https://documentation.open-xchange.com/latest/middleware/http_api.html HTTP API]
	<!-- it's still the same, don't fork it, it will diverge way too fast with fixes still done for OX6 -->		<!-- it's still the same, don't fork it, it will diverge way too fast with fixes still done for OX6 -->

Tierlieb: Redirected page to HTTP API

2013-08-06T08:03:20Z

Redirected page to HTTP API

Show changes

Marcus.klein: described data type for actual and target costs for tasks

2013-08-01T14:09:46Z

described data type for actual and target costs for tasks

← Older revision		Revision as of 14:09, 1 August 2013
Line 858:		Line 858:
	\| 301 \|\| percent_completed \|\| Number \|\| How much of the task is completed. An integer number between 0 and 100.		\| 301 \|\| percent_completed \|\| Number \|\| How much of the task is completed. An integer number between 0 and 100.
	\|-		\|-
	\| 302 \|\| actual_costs		\| 302 \|\| actual_costs \|\| Number \|\| A monetary attribute to store actual costs of a task. Allowed values must be in the range -9999999999.99 and 9999999999.99.
	\|-		\|-
	\| 303 \|\| actual_duration		\| 303 \|\| actual_duration
Line 866:		Line 866:
	\| 305 \|\| billing_information		\| 305 \|\| billing_information
	\|-		\|-
	\| 307 \|\| target_costs		\| 307 \|\| target_costs \|\| Number \|\| A monetary attribute to store target costs of a task. Allowed values must be in the range -9999999999.99 and 9999999999.99.
	\|-		\|-
	\| 308 \|\| target_duration		\| 308 \|\| target_duration

Martin.schneider: /* Redeem Token (since 7.4.0) */

2013-06-19T14:08:42Z

Redeem Token (since 7.4.0)

← Older revision		Revision as of 14:08, 19 June 2013
Line 172:		Line 172:
	Parameters:		Parameters:
	* <code>token</code> – The token created with [[#Get_a_login_token \| acquireToken]].		* <code>token</code> – The token created with [[#Get_a_login_token \| acquireToken]].
	* <code>authId</code> – Identifier for tracing every single login request passed between different systems in a cluster. The value should be some token that is unique for every login request.		* <code>authId</code> – Identifier for tracing every single login request passed between different systems in a cluster. The value should be some token that is unique for every login request. This parameter must be given as URL parameter and not inside the body of the POST request.
	* <code>client</code> – Identifier of the client using the HTTP/JSON interface. The client must identifier must be the same for each request after creating the login session.		* <code>client</code> – Identifier of the client using the HTTP/JSON interface. The client must identifier must be the same for each request after creating the login session.
	* <code>secret</code> – The value of the secret string for token logins. This is configured through the tokenlogin-secrets configuration file.		* <code>secret</code> – The value of the secret string for token logins. This is configured through the tokenlogin-secrets configuration file.

Martin.schneider: /* Redeem Token (since 7.4.0) */

2013-06-19T14:06:22Z

Redeem Token (since 7.4.0)

← Older revision		Revision as of 14:06, 19 June 2013
Line 176:		Line 176:
	* <code>secret</code> – The value of the secret string for token logins. This is configured through the tokenlogin-secrets configuration file.		* <code>secret</code> – The value of the secret string for token logins. This is configured through the tokenlogin-secrets configuration file.

	Response: A JSON object containing the session ID used for all subsequent requests. Additionally a random token is contained to be used for the Easy Login method.		Response: A JSON object containing the session ID used for all subsequent requests. Additionally a random token is contained to be used for the Easy Login method. If configured within tokenlogin-secrets configuration file even the user password will be returned.

	== Module "config" ==		== Module "config" ==

Martin.schneider: /* Redeem Token (since 7.4.0) */

2013-06-19T13:47:47Z

Redeem Token (since 7.4.0)

← Older revision		Revision as of 13:47, 19 June 2013
Line 173:		Line 173:
	* <code>token</code> – The token created with [[#Get_a_login_token \| acquireToken]].		* <code>token</code> – The token created with [[#Get_a_login_token \| acquireToken]].
	* <code>authId</code> – Identifier for tracing every single login request passed between different systems in a cluster. The value should be some token that is unique for every login request.		* <code>authId</code> – Identifier for tracing every single login request passed between different systems in a cluster. The value should be some token that is unique for every login request.
	* <code>client</code> – Identifier of the client using the HTTP/JSON interface. The client must be the same ~~as those of~~ the ~~client requested the token~~.		* <code>client</code> – Identifier of the client using the HTTP/JSON interface. The client must identifier must be the same for each request after creating the login session.
	* <code>secret</code> – The value of the secret string for token logins. This is configured through the tokenlogin-secrets configuration file.		* <code>secret</code> – The value of the secret string for token logins. This is configured through the tokenlogin-secrets configuration file.