---
alias: user-guide-post-iot-event
description: "Post IoT events conforming to defined schemas, triggering data updates within the system"
---

# Post IoT Event

:lock: IoTEventDefinition.**PostEvent**

## Overview

This operation is used to post an **IoT Event** whose payload must conform to the schema defined in the corresponding **IoT Event Definition**.

## Setup

No specific setup is required other than to meet the preconditions of the transaction.

## Preconditions

* The **IoT Event Definition** exists in the system and is in the Active state.

## Sequence of Steps

To manually post an IoT Event, follow these steps:

1. Open an existing **IoT Event Definition** (either user-created or system-created).
2. On the **IoT Event Definition** page, select the **Post** button on the top ribbon.
3. Optionally, specify an **Event Time** if the event should be posted with a specific date and time.
4. Select the **Application Name**. The default value is `GUI HTML`.
5. Optionally, provide an Application Context.
6. Optionally, select the **Data Silo** associated with the **IoT Event Definition**.

    !!! info
        The Data Silo option is only available with an Enterprise Data Platform license is enabled. For more information, see [[installation-guide-edpconnector]].

7. Optionally, upload a File containing the data to be posted.
8. Enter the JSON payload for the event.

    !!! info "Missing Property in JSON Payload"
        If an event is posted without one or more required properties, the wizard completes successfully but displays a warning. The warning message explicitly identifies the name of the missing required property (for example, `#PropertyRequired: #/Values`). This warning indicates that the event was published to an error topic. Therefore, if a Data Set is associated with the IoT Event Definition, the event will not be ingested into ClickHouse and will not be available in the corresponding tables.

        ![Post IoT Event Warning](images/post_event_warning.png)

9. Select **Post** to submit the event.

=== "Without EDP License"

    ![Post IoT Event](images/post_iot_event.png)

=== "With EDP License"

    ![Post IoT Event](images/edp_post_iot_event.png)

After the event is posted, the data is available in the Data section of the [[user-guide-data-set-page]] associated with the selected IoT Event Definition.

!!! info
    Alternatively, you may use the [[user-guide-automation-task-core-apipostevent]] task.

## Known Limitations

### Large Numeric Values in JSON Payload

Very long numeric values (such as IDs) in the JSON payload may be silently corrupted — the last few digits can be replaced by zeros. For example, `264090000467654321` may become `264090000467654000`.

To avoid this, wrap long numeric values in quotes:

```json
"UserId": "264090000467654321"
```

!!! note "Technical Background"
    This is caused by a known limitation of the `JSON.parse` library. For more details, see [Why does JSON.parse corrupt large numbers?](https://jsoneditoronline.org/indepth/parse/why-does-json-parse-corrupt-large-numbers/).