> This page is for Home.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.emnify.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.emnify.com/_mcp/server.

> Custom events in the emnify platform

| ID | Description       |
| :- | :---------------- |
| 72 | [Custom](#custom) |

> **API reference**
>
> The configured parameters of a custom event are in the event's [detail object](/developers/reference/events#detail-object).

### Custom

A [custom event](/portal/automations#custom-events) configured in your Workspace was triggered.

Unlike system events, custom events are based on templates that you configure with your own parameters, such as a data traffic threshold or a severity level.
All custom events share the same event type `Custom` (ID `72`), no matter which template they're based on.
To identify which custom event was triggered, use the `template_id` property of the `detail` object.

Because custom events are evaluated by the emnify event processing engine, their event source is **Semantic** (ID `3`).
The event severity is the severity you set when [adding the rule](/portal/how-tos/manage-automations#add-a-rule).

The `detail` object of a custom event contains the following properties:

| Property        | Type        | Description                                                                                                |
| :-------------- | :---------- | :--------------------------------------------------------------------------------------------------------- |
| `template_id`   | String      | Identifier of the custom event template the event is based on (for example, `daily-traffic-threshold-v1`). |
| `_meta`         | JSON object | Metadata about the custom event that generated this event.                                                 |
| `_meta.name`    | String      | Name of the custom event template (for example, `Daily traffic threshold`).                                |
| `_meta.code`    | String      | Unique identifier of the custom event configured in your Workspace.                                        |
| `_meta.id`      | String      | Unique identifier of this occurrence of the custom event.                                                  |
| `_meta.version` | Long        | Version of the custom event configuration.                                                                 |

The remaining properties depend on the template.
For example, the **Daily traffic threshold** template adds the configured threshold (`threshold_volume`) and the volume that was actually consumed (`total_volume`), both in megabytes (MB).

> **Note**
>
> Custom events are also listed in the emnify Portal alongside system events.
> See [Custom events in the events log](/portal/automations#custom-events-in-the-events-log).

#### Example JSON response: daily traffic threshold reached

```json maxLines=10
{
  "timestamp": "2026-07-01T11:26:47.638Z",
  "alert": true,
  "description": "Daily endpoint volume threshold of 1 reached for endpoint: Test Sim 2",
  "id": 2555084928745473,
  "event_type": {
    "id": 72,
    "description": "Custom"
  },
  "event_source": {
    "id": 3,
    "description": "Semantic"
  },
  "event_severity": {
    "id": 0,
    "description": "INFO"
  },
  "organisation": {
    "id": 1572,
    "name": "Test Org"
  },
  "user": null,
  "endpoint": {
    "id": 18018628,
    "name": "Test Sim 2",
    "ip_address": "10.192.200.49",
    "tags": "monitoring",
    "imei": "3530570910841456"
  },
  "sim": null,
  "imsi": null,
  "detail": {
    "_meta": {
      "code": "019d0bec-2688-776f-b30e-c282580b1720",
      "id": "019d0bec-2688-776f-b30e-c282580b1720_1774021520051",
      "version": 1775649028911,
      "name": "Daily traffic threshold"
    },
    "threshold_volume": "1",
    "total_volume": "24.586832",
    "template_id": "daily-traffic-threshold-v1"
  }
}
```