> 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. > Manage events with emnify's Data Streamer, REST API, or Portal There are three ways you can access and trigger available events: * [Data Streamer](#data-streamer) * [Event API](#event-api) * [emnify Portal](#emnify-portal) ## Data Streamer The emnify Data Streamer allows you to configure data streams that capture events generated by the emnify system. These events can include billing-related updates, SIM orders, and other operations your users perform. You gain full network transparency by leveraging integrations to identify and address issues quickly. Additionally, you can use the provided information to develop your applications or business logic. These integrations offer valuable insights for IoT remote monitoring, anomaly detection, detailed service usage data (data and SMS), and cost per device. > **Tip** > > See the [Data Streamer documentation](/multicloud-data-streamer) to learn more about its benefits and how to get started. ### Manage event data streams in the Portal To manage your data streams, log in to your [emnify Portal](https://portal.emnify.com/) account. Then, navigate to the [**Data Streams**](https://portal.emnify.com/integrations#data-streams) section of the [**Integrations** page](https://portal.emnify.com/integrations). If no data streams are configured, the **Data Streams** panel displays all available connection types as tiles. If you already have a data stream configured, the panel displays all existing streams, ordered by creation date (newest on the top). This list view can be used to gain an overview of the current states of different data streams. Data streams marked as **Running** are properly operating. Failed streams exhibit an **Error** status. Paused streams are marked as **Paused**. ![Data streams list with Running, Paused, and Error status labels and a Details button on each row](/_fern-img/59b5a8672cfdaf7ca3280d50ae154ebd34105ae519abf9c7b3e4ec76e8285850.webp) The **Details** button allows you to inspect the configuration of the specific stream. > **Note** > > You can distinguish event data streams by checking if the **Stream Type** on a specific data stream is set to **Stream events**. The Data Streamer can apply filtering for event data streams based on event types. Under **Event Options**, you can choose to **Stream all events** or **Stream specific events only**. Selecting the latter displays a searchable dropdown listing all [event types](/system-events/event-types) available as filters. ![Event stream details with Stream specific events only selected and an Update location filter](/_fern-img/79294b45539c2b4393e0ee34254db6bed7d2c0e31b89a2b92ca3582af20044db.webp) > **Tip** > > Using the Portal, you can also create, update, and delete data streams. > Learn more in the [Data Streamer usage documentation](/multicloud-data-streamer/usage#data-streamer-in-the-portal). ## Event API The [emnify REST API](/developers/api) provides a variety of HTTP requests for integrating several emnify services into your application, including the ability to trigger and monitor events. The [Event API](#retrieve-events-with-the-event-api) specifically allows you to search for recent events and supports various types of result filtering. > **Warning** > > For events, the emnify REST API uses a [pull architecture](https://dev.to/anubhavitis/push-vs-pull-api-architecture-1djo), which means you're responsible for requesting updates and retrieving new events. > If you prefer real-time updates, consider using the [emnify Data Streamer](#data-streamer). ### Authentication To use the emnify API, you must authenticate with an authentication token. emnify uses JSON Web Tokens (JWTs) for the authentication tokens. > **Tip** > > The [Getting Started guide in the Developers documentation](/developers) provides step-by-step instructions for retrieving your authentication token. ### Specification and documentation The emnify REST API is based on the OpenAPI Specification 3.0 (OAS3). We also offer [interactive API documentation](/developers/api). > **Tip** > > Prior OpenAPI knowledge isn't necessary to work with the emnify API. > However, understanding [how an OpenAPI Specification is structured](https://spec.openapis.org/oas/latest.html) could help you navigate the documentation. The [Events Reference page](/developers/reference/events) in the Developers documentation provides detailed information about the event structure and common elements you'll encounter using the Event API. ### Retrieve events with the Event API The following entry points are available for retrieving a list of the events or event types available to your organization: | Method | Entry point | Description | | ------ | ----------------------------------------------------------- | -------------------------------------------------------------------------------------- | | `GET` | [/api/v1/event](/developers/api/events/get-events) | Returns the list of events, filtered, sorted, and paged according to query parameters. | | `GET` | [/api/v1/event/type](/developers/api/events/event-type-get) | Provides the list of `event_types` (lookup). | You can also list events for specific endpoints, SIMs, or users using the following entry points. These event lists can be filtered, sorted, and paged according to query parameters. | Method | Entry point | Description | | ------ | ------------------------------------------------------------------------------------------------------------------- | ------------------------------------ | | `GET` | [/api/v1/endpoint/\{endpoint_id}/event](/developers/api/endpoint/endpoint-events-by-id) | Returns the list of endpoint events. | | `GET` | [/api/v1/sim/\{sim_id}/event](/developers/api/sim/sim-event-page-per-page-sort-by-sim-id-and-q-get) | Returns the list of SIM events. | | `GET` | [/api/v1/user/\{user_id}/event](/developers/api/user-management/user-event-page-per-page-sort-by-user-id-and-q-get) | Returns the list of user events. | ## emnify Portal There are several ways to view or trigger events within the [emnify Portal](https://portal.emnify.com/). ### Events in the Portal Here's where you can find event information in the Portal: | Destination | Event information | | ------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | [**Dashboard**](https://portal.emnify.com/) | Overview of all event activity within your organization. ![Dashboard Events table with severity, date, event source, event type, device, network, and country columns](/_fern-img/8611a4e28687f5326d331d3d57e53fd0e44d2b6c5bfd0d9ad98ac5bae6f39e9b.webp) | | [**Connected Devices**](https://portal.emnify.com/connected-devices) > Click on a device to open its details > **Events** | List of triggered events for a particular device (also referred to as an "endpoint"). ![Device Events tab with filters and a table of event types, networks, and countries](/_fern-img/cb8f25cf0798375bc336ffd6fe678eff1a3a62611ef77becbe18b4ff683f7a90.webp) | | [**SIM Inventory**](https://portal.emnify.com/sim-inventory) > **Details** > **Events** | List of triggered events for a particular SIM card. ![SIM Events tab listing SIM activation and SIM Assigned events](/_fern-img/11d941a5186acde94e1770692fd6b0ef42c571beced691a821524582b29d3274.webp) | > **Note** > > Any events triggered in the Portal show **API** as the [event source](/system-events#event-source). ### Available data for individual events No matter where you view events in the Portal, you'll have access to the following information for each event. | Property | Description | | ------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Severity | The [event severity](/system-events#event-severity). | | Date | A timestamp the event was triggered. By default, the Portal shows the relative date (for example, "a day ago," "15 days ago," "a month ago"). Pressing the clock icon shows an absolute date value in the `MMMM dd, yyyy hh:mm a` format. | | Event Source | Which [system triggered the event](/system-events#event-source). | | Event Type | Name of the triggered event (the `description` value in the [Event type object](/developers/reference/events#event-type-object)). This field also indicates the network generation (4G, 5G, etc.) for specific events, like [PDP context lifecycles](/system-events/event-types/data-connection-lifecycle). | | Device | Name of the device impacted by the event (the `name` value from the [Endpoint object](/developers/reference/events#endpoint-object)). This name often links to the device's entry on the [**Connected Devices**](https://portal.emnify.com/connected-devices) page of the emnify Portal. | | Operator | Which [Mobile Network Operator (MNO)](https://www.emnify.com/blog/mno) the device is currently roaming on (for example, Vodafone, AT\&T). Only listed for relevant network events. | | Country | The country where the MNO listed in the `Operator` field is providing the cellular service. | | ID | A generated unique identifier for the event. | | Description | What happened, why (in some cases), and any additional details associated with the event type. | | Action performed by | The user who performed the action, including their name, email, and user ID. Shown for [device status management events](/system-events/event-types/device-status-management) triggered via the Portal. Actions performed via API or application tokens may not include user details. |