Sign in Schedule a meeting
SensorLogiX
Book a briefingDataLogiX

SENSORLOGIX · FOR DEVELOPERS

Live alerts from the field, in your own system

Everything SensorLogiX does live is an API first, and the console uses the same routes. Follow the alert stream, take signed webhooks, and update the incident you opened when an alert’s status changes.

Read the guidesAPI reference

ALERT STREAM WITH REPLAY · SIGNED WEBHOOKS · TYPESCRIPT AND PYTHON SDKS · READ-ONLY ASSISTANT TOOLS

your dispatch system
// What a receiving system does, one alert at a time
new alert            open an incident, with its status
status changed       update that incident
alert withdrawn      close it, with the reason
back after a restart the alerts it missed replay first
Live alert streamtext/event-stream
1raisedUNVERIFIED zone 3
2changedCORROBORATED seismic S-12
3zone cover lostzone 5 · camera 8
4changedCONFIRMED operator
5sensor lostseismic S-07

THE ONE RULE

One alert, one id

A follow-up never sends a new alert. It changes the status of the one already sent, so your system updates the incident it opened.

ONE ALERT, ONE IDILLUSTRATION

Every follow-up changes the alert you already have

  • New alert · id 7F3AUNVERIFIEDThermal camera 4 · zone 3Your system: Open an incident
  • Status changed · id 7F3ACORROBORATEDSeismic S-12 agreesYour system: Raise its priority
  • Status changed · id 7F3ACONFIRMEDAn operator confirmed itYour system: Dispatch
  • Withdrawn · id 7F3AWITHDRAWNOr: a later check took it backYour system: Close it, with the reason

THE ROUTES

Everything the console does, as routes

With the conventions of the rest of the DataLogiX API: idempotency keys, signed cursors and one error shape.

ROUTES FOR
WHAT THEY COVER
Detection classes
Which classes your organization has turned on, and their accuracy bars
Zones and rules
Areas, schedules and rules; test a rule against the last hour
Alerts and status history
Each alert with its sources, clip, location, rule and every change
Incidents
Grouped alerts, timeline, assignment and dispatch state
Sensors and coverage
Inventory, health, heartbeats and the coverage map
Collector boxes
Streams, GPU, disk, link and events waiting
Camera holds and requests
Hold and release a fixed camera for a short time, and send a look-here request
Teams and sectors
Teams, sectors and the scope each person starts in
Recordings
Search clips, and fetch footage from a box
Notification rules
Who gets which alert, and when it escalates
Metrics
Alerts by zone, response times, false alarms, uptime, accuracy by class
Shadow mode
Hold a site’s alerts while an operator marks them
Read the guides

STREAM AND WEBHOOKS

Take alerts the way your system works

The live alert stream

Server-sent events, like every DataLogiX stream. Reconnect with the last event id and the alerts you missed replay, so a dispatch system that restarts picks up where it left off.

  • Filter it. By zone, class or status, so a receiver can act only on corroborated or confirmed alerts.
  • Read the history. Every change to an alert, in order, with who or what made it.

Webhooks

Signed like every DataLogiX webhook, with retries and a delivery log, for each of these:

  • New alertWith its status
  • Status changedIts status or evidence changed
  • WithdrawnRejected by a person, or taken back by a later check
  • Sensor lostA sensor or box stopped reporting
  • Zone cover lostA zone no longer has the sensors it needs

STATUS IS DATA

What each alert carries

Status and its history

Unverified, corroborated, confirmed or withdrawn, and each change with its time and its source.

Sources

The sensors and models that saw it, and the person who confirmed it.

Evidence

The clip, the location and the rule that fired, each with a link back.

Markings

The alert’s marking, applied before it leaves, under your dissemination rules.

AI ASSISTANTS

Read-only tools for assistants

Assistants list and read alerts within the signed-in person’s rights, through the DataLogiX MCP server. No tool changes a zone, a rule or a status, or holds a camera.

  • Guides for every step. Zones, alert status, the API, connecting each kind of sensor, installing a box, shadow mode and retention.
  • Your own equipment? The integration guides, sample payloads, conformance tool and simulators are on the equipment makers’ page.
For equipment makers

Put live alerts in what you build

Tell us which system should take them; we’ll show the stream and the webhooks against a sandbox.

Talk to an engineerDataLogiX for developers