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:
https://api.twinview.com/twinview/devices/event
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
{
"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:
{Sucess}
If the payload is unsuccessful, Twinview will return the response:
{Error}