Events
It is envisioned that the caller will receive events on a near-real-time basis from the source system (MQ) and in response, will call the REST API with individual events. Batches of events will also be supported with a single call to the API. It is assumed that events will be sent in order such that an API call will not be made that contains events older than a previous API call. The events within the call (if they are batched) do not necessarily need to be in order, but once a call is made, all subsequent calls need to be at or after the largest timestamp in the previous call.
This page includes the following:
Requests
You can use the following event requests:
HTTP Verb | Resource | Input | Expected Output (HTTP/1.1) |
---|---|---|---|
POST | /events | { “transactionId” : [String], “schedulerId” : [String], “data” : [{“eventTime” : [Long], “properties” : [{“propertyName”: [String], “propertyValue” : [String], “propertyType” : [String] }] }] } |
Success Code: 201 Created Content: { itemsProcessed : [int] } |
POST | /resourceEvent | { “transactionId” : [String], “data” : [{“type”:[String] “eventTime” : [Long], “resourceName” : [String], “resourceType” : [String], “properties” : [{“propertyName”: [String], “propertyValue” : [String], “propertyType” : [String] }] }] } |
Success Code: 201 Created Content: { "message": "Events processed: [int], "success": true } |
Event Data Dictionary
-
schedulerId
Allowed values: Any valid JAWS schedulerId
Only used for non transactional event processors(Custom AutoSys)
-
eventTime
Seconds or milliseconds since epoch
-
properties
Allowed values: See Appendix B - Event Properties and Usage
-
transactionId
Only used for non transactional event processors(Non Custom AutoSys)