v1API ReferenceOperators

Delete an operator

Delete an operator from the roster. Production logs and shifts that reference the operator are left pointing at a record that no longer resolves, so for someone who has simply left, leaving the record in place preserves the history their shifts are attached to.

Path Parameters

operator_id*Operator Id

The operator ID.

Response Body

application/json

Try it live
DELETE
/v1/operators/{operator_id}

This endpoint requires authentication — paste a token in the Authorization section below.

curl -X DELETE "https://example.com/v1/operators/0"
Empty

Update an operator PATCH

Partially update an operator: send only the fields that change.

Create Production Logs POST

Create one or many Production Logs. The body is a JSON **array**, even for a single record. This is the endpoint an MES, ERP or shop-floor terminal uses to push production into Pulsar. `machine` and `sku` are references that accept either an `id` or a `name`, so a system that only knows line names and product codes does not have to resolve Pulsar ids first. A Production Log describes a closed interval: `start` and `end` are both required. To record what is happening in the shift a machine is running right now, use the realtime endpoints instead.