-
Notifications
You must be signed in to change notification settings - Fork 0
API
Your Name edited this page Jun 24, 2026
·
4 revisions
Home | Overview | Architecture | API | Operations | Validation-Guide
All JSON endpoints are served under /api/.
| Method | Path | Purpose |
|---|---|---|
| GET | /api/sensors/ |
List sensors |
| GET | /api/readings/recent/?limit=50 |
Return recent readings |
| GET | /api/sensors/<id>/readings/?limit=100 |
Return readings for one sensor |
| GET | /api/alerts/active/ |
Return active alerts |
| GET | /api/summary/ |
Return operational summary |
| GET | /api/health/sources/ |
Return telemetry source status |
- Reading payloads include
source, a short lineage field such assimulator:seed=42ormodbus:host:port - Legacy bare API routes without
/api/are not part of the public contract - The source health endpoint is operational metadata; it does not replace a live Modbus connectivity test
The recent readings endpoint returns a compact operational payload:
sensor_nameparameterraw_valuecalibrated_valuesourcestatus
curl -s http://127.0.0.1:8000/api/summary/
curl -s http://127.0.0.1:8000/api/health/sources/