Ingest device and point data

Send data from your system into KODE OS by registering devices on a KODE API data source and posting point values. KODE OS then treats your data like any other connected building data. Each linked endpoint can switch the sample between cURL, JavaScript, Python, and PowerShell, or send the request for you.

Before you begin

You need:

An access token. See the quickstart.
A buildingId from List buildings.
A data source with apiType set to API_KODE on that building. Ask your KODE project team to create one if it does not exist.

Send device data

Find your data source

Call List building data sources and note the _id of the data source whose apiType is API_KODE.

curl "https://api.kodelabs.com/kodeos/api/v1/buildings/${BUILDING_ID}/integrations/datasources" \
  --header "Authorization: Bearer ${KODE_ACCESS_TOKEN}"

Create devices and points

Register each device with its points. Use stable identifiers from your system, because sending the same id again updates the existing device instead of creating a duplicate.

curl --request POST \
  "https://api.kodelabs.com/kodeos/api/v1/buildings/${BUILDING_ID}/integrations/datasources/${DATASOURCE_ID}/devices/batch" \
  --header "Authorization: Bearer ${KODE_ACCESS_TOKEN}" \
  --header "Content-Type: application/json" \
  --data '{
    "devices": [
      {
        "id": "ahu-01",
        "name": "AHU-01",
        "points": [
          { "pointId": "supply-air-temp", "name": "Supply Air Temp", "kind": "Number", "unit": "°F" },
          { "pointId": "fan-status", "name": "Fan Status", "kind": "Bool" }
        ]
      }
    ]
  }'

The response reports how many devices and points were created or updated:

{ "deviceSize": 1, "pointsSize": 2 }

Send current values

Post values grouped by device. Set timestamp to the Unix epoch time of the measurement, or 0 to use the current time.

curl --request POST \
  "https://api.kodelabs.com/kodeos/api/v1/buildings/${BUILDING_ID}/integrations/datasources/${DATASOURCE_ID}/timeseries" \
  --header "Authorization: Bearer ${KODE_ACCESS_TOKEN}" \
  --header "Content-Type: application/json" \
  --data '{
    "data": [
      {
        "deviceId": "ahu-01",
        "points": [
          { "id": "supply-air-temp", "value": 55.4, "timestamp": 1759840200, "status": "ok" },
          { "id": "fan-status", "value": true, "timestamp": 1759840200, "status": "ok" }
        ]
      }
    ]
  }'

Confirm the values arrived

Call List latest point values with the KODE OS point identifiers returned by List building points.

Choose a timeseries endpoint

Endpoint	Use it when
Send timeseries for a data source	You send values for many devices at once.
Send timeseries for a device	You send values for one device at a time.
Send historical values for a point	You backfill history for a single point.

Design for reliable ingestion

Batch values to stay within the rate limits. Five requests per second is the burst ceiling.
Send the measurement time, not the time your service processed the value.
Use status to report fault, down, or no_value instead of skipping a reading.
Re-run device creation when your system adds points. Existing devices update in place.

Get started

Guides

API reference

Before you begin

Send device data

Choose a timeseries endpoint

Design for reliable ingestion

​Before you begin

​Send device data

​Choose a timeseries endpoint

​Design for reliable ingestion

Before you begin

Send device data

Choose a timeseries endpoint

Design for reliable ingestion