---
title: The Twinview Data Ingestion service
description: This guide explains the core data ingestion service that consumes data into the Twinview high-performance Datalake.
---

[Skip to content](https://content.twinview.com/knowledge-base/iot-setup-and-integration/the-twinview-data-ingestion-service#main-content)

English

Show submenu for translations

[![Twinview Academy - Purple Background (3).png\]](https://content.twinview.com/hs-fs/hubfs/Twinview%20Academy%20-%20Purple%20Background%20(3).png?height=50&name=Twinview%20Academy%20-%20Purple%20Background%20(3).png)](https://content.twinview.com/knowledge-base?hsLang=en)

Open main navigation

Close main navigation

- English
  
  Show submenu for translations
- [Go to twinview.com](https://www.twinview.com/)

[Go to twinview.com](https://www.twinview.com/)

 Welcome To The Twinview Knowledge Base

- There are no suggestions because the search field is empty.

1. [IoT Setup & Integrations](https://content.twinview.com/knowledge-base/iot-setup-integrations?hsLang=en)

# The Twinview Data Ingestion service

## This guide explains the core data ingestion service that consumes data into the Twinview high-performance Datalake.

You can send your data directly to the Twinview Data ingesting service. This stores the data in the Twinview high-performance datalake. The ingestion service is used by the Twinview gateway to publish data to Twinview. However, it can be used stand-alone if required.

The following methods are supported and available for use:

 

|  | Port | Security | METHOD |
| --- | --- | --- | --- |
| HTTP Web Request | 80 |  | POST |
| HTTPS Web Request | 443 | TLS 1.3 or SSL | POST |
| MQTT (Secure) | 8883 or 443 | TLS 1.3 | PUBLISH |

#### Publishing data to the service

You can publish data to the ingestion service by HTTPS web request or by Publishing the MQTT ingestion topic.

### HTTP Web Request

The end ingestion end points to publish data to is:

POST

```
https://api.twinview.com/twinview/devices/event
```

POST

```
https://ingestion.twinview.com/twinview/devices/event
```

#### Payload format

The payload should contain the IOT Datastream Device identifier (UUID) and the value to be submitted (state). The payload should only contain one UUID and one state

**Example JSON Payload**

```
{    "uuid": "88779ad4-3c08-426b-a2e4-7a4d973344d26",    "state": "22.5"}
```

- **uuid :** this is the uuid of the Twinview device in IOT Data Stream Device
- **state:** is the value

#### Responses

If the payload is accepted by Twinview and successful, Twinview will return the response:

200 Sucess

```
{Sucess}
```

If the payload is unsuccessful, Twinview will return the response:

400 Bad Request

```
{Error}
```

- [Getting started](https://content.twinview.com/knowledge-base/getting-started?hsLang=en)
- [User Interface & Navigation](https://content.twinview.com/knowledge-base/user-interface-navigation?hsLang=en)
- [Asset & Information Management](https://content.twinview.com/knowledge-base/asset-information-management?hsLang=en)
- [Facilities Management Toolkit](https://content.twinview.com/knowledge-base/facilities-management-toolkit?hsLang=en)
- [IoT & Analytics Module](https://content.twinview.com/knowledge-base/iot-analytics-module?hsLang=en)
- [IoT Setup & Integrations](https://content.twinview.com/knowledge-base/iot-setup-integrations?hsLang=en)
- [Node Assistant](https://content.twinview.com/knowledge-base/node-assistant?hsLang=en)
- [Training Excercises](https://content.twinview.com/knowledge-base/training-excercises?hsLang=en)
- [Appendix Documents](https://content.twinview.com/knowledge-base/appendix-documents?hsLang=en)

[![Twinview\_BLACK\_RGB](https://content.twinview.com/hs-fs/hubfs/Twinview_BLACK_RGB.png?width=200&height=78&name=Twinview_BLACK_RGB.png "Twinview_BLACK_RGB")](https://content.twinview.com/knowledge-base?hsLang=en)

Copyright © 2026, Twinview