Core API - Revision history

WikiAdmin at 22:46, 26 March 2014

2014-03-26T22:46:47Z

WikiAdmin at 17:45, 26 March 2014

2014-03-26T17:45:17Z

WikiAdmin at 17:42, 26 March 2014

2014-03-26T17:42:43Z

WikiAdmin at 18:30, 4 March 2014

2014-03-04T18:30:32Z

WikiAdmin at 18:29, 4 March 2014

2014-03-04T18:29:58Z

188.107.134.155 at 09:16, 5 September 2012

2012-09-05T09:16:26Z

188.107.134.155 at 08:37, 5 September 2012

2012-09-05T08:37:57Z

188.107.134.155 at 08:37, 5 September 2012

2012-09-05T08:37:45Z

WikiAdmin at 09:19, 4 September 2012

2012-09-04T09:19:06Z

WikiAdmin at 08:15, 4 September 2012

2012-09-04T08:15:40Z

@@ Line 6: / Line 6: @@
-==Event management==
+=System API Downloads=
 A really important feature to track all domain-transactions. Normally you can poll all domain-events by using the commands: <code>[[StatusEvent|StatusEvent]]</code>, <code>[[QueryEventlist|QueryEventlist]]</code> and <code> [[DeleteEvent|DeleteEvent]]</code>. Alternatively you can use the option <code>[[EventsPop3|Receive Events over POP3]]</code>. Please note that you should always choose only one method  to avoid inconstancies.
@@ Line 14: / Line 19: @@
-==System API error codes==
+=System API error codes=
 Please find below a list of all API - Error CODES:
 *[[API:ErrorCodes | API-ERROR CODES]]
-==Usage restrictions==
+=Usage restrictions=
 *[[API:QuotaSystem | System Usage Restrictions (Quota Regulation)]]
-==Core API commands==
+=Core API commands=
 '''Download:''' {{Template:Pdf|CORE_API_Reference.pdf| Core API manual}} (Version 2.6)

← Older revision		Revision as of 17:45, 26 March 2014
Line 25:		Line 25:
	==Core API commands==		==Core API commands==

−	'''Download:''' {{Template:Pdf\|CORE_API_Reference.pdf\| Core API manual}}	+	'''Download:''' {{Template:Pdf\|CORE_API_Reference.pdf\| Core API manual}} (Version 2.6)

← Older revision		Revision as of 17:42, 26 March 2014
Line 25:		Line 25:
	==Core API commands==		==Core API commands==

−	~~{{Infobox\|~~Download: {{Template:Pdf\|CORE_API_Reference.pdf\| Core API manual}}}}	+	'''Download:''' {{Template:Pdf\|CORE_API_Reference.pdf\| Core API manual}}

← Older revision		Revision as of 18:30, 4 March 2014
Line 19:		Line 19:


−	==~~System usage~~ restrictions==	+	==Usage restrictions==
	*[[API:QuotaSystem \| System Usage Restrictions (Quota Regulation)]]		*[[API:QuotaSystem \| System Usage Restrictions (Quota Regulation)]]

@@ Line 1: / Line 1: @@
-{{Sidebar}}__NOTOC__
+{{Sidebar}}
-<h2>Event management</h2>
+<div style="font-size: 160%;">System API</div>
 A really important feature to track all domain-transactions. Normally you can poll all domain-events by using the commands: <code>[[StatusEvent|StatusEvent]]</code>, <code>[[QueryEventlist|QueryEventlist]]</code> and <code> [[DeleteEvent|DeleteEvent]]</code>. Alternatively you can use the option <code>[[EventsPop3|Receive Events over POP3]]</code>. Please note that you should always choose only one method  to avoid inconstancies.
@@ Line 8: / Line 14: @@
-<h2>System API error codes</h2>
+==System API error codes==
 Please find below a list of all API - Error CODES:
 *[[API:ErrorCodes | API-ERROR CODES]]
-<h2>System usage restrictions</h2>
+==System usage restrictions==
 *[[API:QuotaSystem | System Usage Restrictions (Quota Regulation)]]
-<h2>Core API commands</h2>
+==Core API commands==
 {{Infobox|Download: {{Template:Pdf|CORE_API_Reference.pdf| Core API manual}}}}

← Older revision		Revision as of 09:16, 5 September 2012
Line 3:		Line 3:

	A really important feature to track all domain-transactions. Normally you can poll all domain-events by using the commands: <code>[[StatusEvent\|StatusEvent]]</code>, <code>[[QueryEventlist\|QueryEventlist]]</code> and <code> [[DeleteEvent\|DeleteEvent]]</code>. Alternatively you can use the option <code>[[EventsPop3\|Receive Events over POP3]]</code>. Please note that you should always choose only one method to avoid inconstancies.		A really important feature to track all domain-transactions. Normally you can poll all domain-events by using the commands: <code>[[StatusEvent\|StatusEvent]]</code>, <code>[[QueryEventlist\|QueryEventlist]]</code> and <code> [[DeleteEvent\|DeleteEvent]]</code>. Alternatively you can use the option <code>[[EventsPop3\|Receive Events over POP3]]</code>. Please note that you should always choose only one method to avoid inconstancies.
		+

	HEXONET informs you via email about all events via the <code> [[PushEvents\|PushEvents]]</code> feature. PushEvents is an additional event messaging service to store and process all product-related events on your side. Inform your client about outgoing/incoming transfers, successful registrations and many more. It can also be used as a backup solution for your own security.		HEXONET informs you via email about all events via the <code> [[PushEvents\|PushEvents]]</code> feature. PushEvents is an additional event messaging service to store and process all product-related events on your side. Inform your client about outgoing/incoming transfers, successful registrations and many more. It can also be used as a backup solution for your own security.

← Older revision		Revision as of 08:37, 5 September 2012
Line 18:		Line 18:
	<h2>Core API commands</h2>		<h2>Core API commands</h2>

−	{{Infobox\|Download: {{Template:Pdf\|CORE_API_Reference.pdf\| Core API}}}}	+	{{Infobox\|Download: {{Template:Pdf\|CORE_API_Reference.pdf\| Core API manual}}}}

← Older revision		Revision as of 09:19, 4 September 2012
Line 16:		Line 16:


−	<h2>API commands</h2>	+	<h2>Core API commands</h2>

	Download: {{Template:Pdf\|CORE_API_Reference.pdf\| Core API}}		Download: {{Template:Pdf\|CORE_API_Reference.pdf\| Core API}}