Connect Sensors and Devices

By the end of this guide a device you own — a microcontroller, a gateway, or a webhook from a platform you already run — will be posting readings onto a Vynta asset, and those readings will be counting towards its health score.

Who this is for. Admins and managers: the key is issued under Settings → Sensors & Predictions. Anyone who writes firmware or automations can do the posting — there is nothing to install on the device side beyond an HTTP POST.

What You Need

Get an ingest key

Issue it in Settings → Sensors & Predictions. It is shown once, so copy it when it appears.

Get an asset ID

Use the copy button beside each asset on the same settings page.

Have something that can POST JSON over HTTPS

That is the whole requirement.

The Endpoint

POST https://vyntaintegrate.com/api/public/sensors/readings
content-type: application/json
x-sensor-key: YOUR_KEY

The body is a batch of readings:

{
  "readings": [
    {
      "equipment_id": "ASSET_UUID",
      "metric": "temperature_c",
      "value": 41.2,
      "unit": "°C",
      "recorded_at": "2026-09-21T06:15:00Z"
    }
  ]
}

equipment_id — the asset’s ID. Only assets in your own business are accepted.
metric — one of temperature_c, pressure_kpa, vibration_mm_s, runtime_hours, error_codes.
value — the number. unit is optional, 20 characters max.
recorded_at — any ISO 8601 spelling. Omit it and the server stamps the arrival time; send a time without a zone and it is read as UTC.
Up to 200 readings per request — batch a queue rather than posting once per sample.

Send Your First Reading

Open Settings → Sensors & Predictions

The Connect a device section shows the endpoint and a complete curl example.

Issue a key

The curl example fills in with your key the moment it is issued.

Run it

Swap ASSET_UUID for a copied asset ID and run the command, or paste the key into Send a test reading and press the button.

Confirm

The key row shows Last used the moment the endpoint accepts a batch.

Recipes

ESP32 / Arduino
Raspberry Pi (Python)
Home Assistant
Node-RED
Make, Zapier or any webhook platform

#include <HTTPClient.h>

void pushTemperature(float celsius) {
  HTTPClient http;
  http.begin("https://vyntaintegrate.com/api/public/sensors/readings");
  http.addHeader("content-type", "application/json");
  http.addHeader("x-sensor-key", "YOUR_KEY");
  String body = "{\"readings\":[{\"equipment_id\":\"ASSET_UUID\","
                "\"metric\":\"temperature_c\",\"value\":" + String(celsius) + "}]}";
  http.POST(body);
  http.end();
}

import requests

requests.post(
    "https://vyntaintegrate.com/api/public/sensors/readings",
    headers={"x-sensor-key": "YOUR_KEY"},
    json={"readings": [{
        "equipment_id": "ASSET_UUID",
        "metric": "temperature_c",
        "value": 41.2,
    }]},
    timeout=10,
)

Add a rest_command and call it from an automation:

rest_command:
  vynta_sensor_reading:
    url: "https://vyntaintegrate.com/api/public/sensors/readings"
    method: POST
    content_type: "application/json"
    headers:
      x-sensor-key: "YOUR_KEY"
    payload: '{"readings":[{"equipment_id":"ASSET_UUID","metric":"temperature_c","value":{{ states("sensor.plant_room_temperature") }}}]}'

Point an HTTP request node at the endpoint: method POST, the x-sensor-key header in its Headers tab, and msg.payload shaped as {"readings":[…]} — a Function node before it maps whatever your sensor nodes emit onto equipment_id, metric and value.

Use the HTTP / Webhooks module: POST, JSON body, add the x-sensor-key header, and map your fields onto the payload. The key is header-only by design, so pick a module that supports custom headers.

How Readings Are Used

Readings above their threshold count as fault signals in asset health scoring. Thresholds and per-metric switches live on the same settings page:

A metric switched off still records readings but never affects a score.
Switching an asset off stops its feed entirely without deleting history.
The sample the test button posts is runtime hours, which has no default threshold — connecting can never alarm on its own.

Common Problems

401 Unauthorized

The key is wrong or revoked. Keys are stored hashed — a revoked key cannot be restored; issue a new one and update the device.

404 No matching equipment

The asset ID does not belong to your business, or sensors are switched off for that asset.

400 invalid_payload

The reply lists the index and field that failed — usually a typo in metric or a malformed timestamp.

Readings arrive but the score does not move

They are below threshold, or the metric is switched off — both are by design.

The device cannot reach the endpoint

It is plain HTTPS POST — no VPN, no mTLS. Test the same URL from a laptop with the curl example first.

Work Orders

Scheduling & Dispatch

Customer Portal

Team Management

Inventory & Assets

Time & Attendance

Health & Safety

Reports & Analytics

AI Features

Settings

Connect Sensors and Devices

What You Need

The Endpoint

Send Your First Reading

Recipes

How Readings Are Used

Common Problems

​What You Need

​The Endpoint

​Send Your First Reading

​Recipes

​How Readings Are Used

​Common Problems

What You Need

The Endpoint

Send Your First Reading

Recipes

How Readings Are Used

Common Problems