Docs / Telemetry

Telemetry

Video answers what happened; telemetry answers when to look. Readings are stored against the same timeline as the feed, so a weighbridge event and the footage of the truck on it are one query apart.

What sites usually push

Gate and barrier state	Dry contact, pushed on change. Aligned to the feed so an operator can jump to the frame where a gate opened.
Weighbridge	Numeric reading per weighing event, retained as long as the footage of the same window.
Reefer temperature	Sampled every 60 seconds. Deviations outside the configured band raise an alert.
Door and motion sensors	Pushed on change; used to mark segments worth keeping past the retention window.

Pushing readings

curl -X POST https://<endpoint>/api/v1/plants/gdansk-dc2/telemetry \
  -H "Authorization: Bearer $NORDVIK_SITE_KEY" \
  -H "Content-Type: application/json" \
  -d '{"ts":"2026-08-03T18:42:11Z","readings":{"gate_a":"closed","weighbridge_kg":24180,"reefer_b_c":-18.4}}'

Querying a window

curl -s "https://<endpoint>/api/v1/plants/gdansk-dc2/telemetry?from=2026-08-03T18:00:00Z&to=2026-08-03T19:00:00Z" \
  -H "Authorization: Bearer $NORDVIK_OPERATOR_TOKEN"

Telemetry is independent of the video path: if a camera drops, readings keep arriving, and the gap in footage is visible against a continuous sensor trace. See site feeds for the video side.