> ## Documentation Index
> Fetch the complete documentation index at: https://docs.notifense.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Events

Notifense works by receiving events (or telemetry) from your application to notify end users. Notifense will then send alerts to the channels specified in the alert rules configured on the asset.

## Create events

To create an event, send a request to the `POST /v1/accounts/{accountId}/assets/{assetId}/events` endpoint with the correct request body.

Normally, when an event is created, the Notifense alert rule engine will send out alerts using the alert rules configured for the asset the event was created for. It is also possible to provide a `recipient` and `channel` when creating an event. This bypasses the alert rules configured for the asset and will unconditionally alert *only* the specified recipient through the specified channel.

### Event types

| #  | Name                                         |
| -- | -------------------------------------------- |
| 1  | Any **(cannot be used for creating events)** |
| 2  | InputPowerDisconnected                       |
| 3  | InputVoltageLow                              |
| 4  | BatteryLow                                   |
| 5  | Jammed                                       |
| 6  | MovementStarted                              |
| 7  | MovementStopped                              |
| 8  | IgnitionTurnedOn                             |
| 9  | IgnitionTurnedOff                            |
| 10 | GeofenceEntered                              |
| 11 | GeofenceExited                               |
| 12 | SpeedLimitExceeded                           |
| 13 | AssetLeftBehind                              |
| 14 | FuelLevelLow                                 |
| 15 | AdBlueLevelLow                               |
| 16 | AlarmTriggered                               |
| 17 | LockdownViolated                             |
| 18 | Tampering                                    |
| 19 | CountryBorderCrossed                         |
| 20 | TemperatureHigh                              |
| 21 | TemperatureLow                               |
| 22 | PressureHigh                                 |
| 23 | PressureLow                                  |
| 24 | HardCornering                                |
| 25 | EngineIdling                                 |
| 26 | EngineSpeedLimitExceeded                     |

## Resolving events

Depending on the channel used, when a recipient is contacted by Notifense, the recipient is asked to "resolve" (handle) the event. If the recipient does not resolve the event, the alert rule engine will continue to the next alert rule, if available.

The following event resolutions are available:

| Name     | Effect                                                                                                                                                                                                       |
| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Ignore   | The event is ignored. No further processing takes place.                                                                                                                                                     |
| Disable  | Events of this type will not be processed for this asset for the amount of hours specified. No further processing takes place.                                                                               |
| Escalate | The event is escalated to a recovery specialist who will contact the recipient. Your application will be instructed to start sending real-time telemetry data for this asset (see [Callbacks](./callbacks)). |