Add an operator to the current shift
Assign an operator to the shift the machine is running at the moment of the call.
Both fields are required: operatorId and start, the moment the assignment begins. Use
it for clock-in at a terminal. This writes to the live shift and takes effect immediately.
Path Parameters
The machine ID.
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
curl -X POST "https://example.com/v1/realtime/0/operator" \ -H "Content-Type: application/json" \ -d '{ "operatorId": 1, "start": "2024-01-01T08:00:00" }'Add a SKU to the current shift POST
Attach a SKU to the shift the machine is running at the moment of the call. Built for shop-floor terminals and scanners: no shift lookup and no production-log arithmetic. The SKU is given as `skuId` or as `sku` (its name), and the work order as `simpleWorkOrderId` or `simpleWorkOrderName`. This writes to the live shift and is visible in the Pulsar dashboard immediately.
Metrics report POST
Return OEE, availability, quality and lost minutes per machine and shift. Each row carries the shift indicators (available time, downtime split by cause) together with the derived production metrics: `availability`, `effectiveness`, `quality`, `oee` and `netOee`, plus minutes lost to low speed and to low quality. A `POST` that only reads — the `reports.read` scope is sufficient. Prefer this over deriving OEE from production logs: shift boundaries, downtime classification and counting factors are already applied.