Out of service

Single-file API example

Not connected

The same API login as Cycles. Your bearer session is remembered until logout or expiry; your API key is never stored.

Open this example locally

Save this one file as out-of-order.html. In its folder run python -m http.server 8080 --bind 127.0.0.1, then open http://localhost:8080/out-of-order.html and choose your tenant and environment. Internet access and an updated API are required. Opening the file directly supports the demo only.

Required permissions: OutOfOrder1 (59), Bank Read, Location Read, Unit Read and matching resource grants. Return to service also requires Unit Write. Normal manager and tenant checks apply to every page.

Operational status

Out of service

—

Manual shutdowns, automatic shutdowns and machines under repair, as in DatPro2 OutOfOrder1. Newest changes appear first. Managers with Unit Write can return a machine to service.

Not updated yet

Connect to view your machines, or try the demo.

Machine cards will appear here.

API endpoints used by this example

The API excludes SMS types and disabled locations and enforces resource and retention permissions. It reads the original packed UnitType only. This selection is separate from AutoOutOfOrder alerts and the public machine-error widget.

Return to service records the change in Log2 and verifies Log24. It does not start a machine, clear its recorded error or confirm device acknowledgement. A changed revision returns 409. After an uncertain POST result, refresh and check the status before trying again. POST is never automatically retried.