Webhooks and Notifications
While services are able to analyze vehicle telemetry accessible to them
directly and look for changes of interest,
supports a number of event triggers that allow custom webhooks to be
fired whenever a trigger condition is satisfied, making it easier for
services to receive only the information they are interested in.
The different trigger conditions together with a brief explanation of when they are triggered are outlined in the table below:
||Triggered when the SAE J3016 level of driving automation changes.|
||Triggered when the active Driver is changed throughout the course of a Journey. The Driver may be either a natural person or an autonomous driving system.|
||Triggered when a new Journey is started. Each time the vehicle simulation model is started, a new Journey is begun.|
||Triggered when a Journey is completed. This will be triggered each time the simulation model is stopped.|
||Triggered each time the vehicle location (latitude/longitude) changes. This can be chained together with a reverse geocoding service in order to detect country changes.|
||Triggered any time the ignition status changes.|
||Triggered any time a harsh acceleration event is detected. This is assessed by looking for abrupt changes in the accelerator pedal position across a configurable time interval.|
||Triggered any time a harsh braking event is detected. As with
In addition to their use for external API endpoint notification, triggers can also be configured by the user to raise a visible alert directly within the simulator UI.
Notifications to the simulator are also supported via the
REST API endpoints for external services and applications that wish to
raise alerts in the simulator UI directly. This provides a general
approximation of head unit integration applications can expect to find
in production environments.