Reports a new event that is registered into the historical events, without being evaluated by an alert-definition.
This is typically used to trace what happened outside of the DPS, such as an on-site inspection, a failure reported by a technician or an anomaly detected by an external system.
The payload must identify the thing involved, the severity and the time interval of the event.
The name of the tenant (e.g. acme).
The details of the event being created.
The identifier of the event-definition associated with the event.
The event start timestamp.
The event end timestamp.
The location identifier associated with the event.
The thing identifier associated with the event.
The email of the user who has reported the event.
The text notes in case of User Reported event.
Successfully created.
The event object identifier.
The identifier of the event-definition associated with the event.
The event name.
The event title.
The event description.
The event technical description.
The event start timestamp.
The event end timestamp.
The event severity (1:FAILURE, 2:MAJOR ANOMALY, 3:MINOR ANOMALY, 4:OPERATION, 5:MAINTENANCE).
The customer identifier associated with the event.
The location identifier associated with the event.
The thing identifier associated with the event.
The email of the user who has reported the event.
The text notes in case of User Reported event.
Request data not valid.
The error response.
User not authenticated.
The error response.
User not authorized.
The error response.
API call rate limit exceeded.
The error response.
Internal server error.
The error response.