Machine timeline

Single-file API example · Offline3

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 unit-timeline.html. In its folder run python -m http.server 8080 --bind 127.0.0.1, then open http://localhost:8080/unit-timeline.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: Offline3 (32), Bank Read, Location Read, Unit Read and matching resource grants. Personal categories require additional tabs and User Read. Normal manager and tenant checks apply to every page.

Machine diagnostics

Machine timeline

—

Follow settings, live measurements, states, purchases, resident events, reservations and messages in one chronological view. Open the associated wash document to inspect its graph and measurements.

Connect and paste a machine KID, or try the demo.

Not updated yet

No events loaded.

UTC / MS2000LogSyncField / amountCodeValue / document
Events will appear here.
API operations and access

Offline3 and Bank/Location/Unit Read are required. Tags/Messages require Users2; purchases require Account2; reservations require Bookings1. Those categories also require User Read and a whole-bank grant. Free-text diagnostics need all three personal-data tabs. Without them, numeric/boolean telemetry remains available. The API applies resident visibility and the configured accounting/surveillance limits. Credential, hidden and other-object settings are omitted. Opaque user/message payloads and raw tag credentials are withheld. Explicitly redacted values are not empty source values.

UTC avoids ambiguous daylight-saving times. A page contains at most 100 events in this example; the API supports up to 200. The interval is at most 24 hours. Cursors expire after 15 minutes; refresh to restart. Late arrivals appear on refresh. No database changes or messages are sent. Graphs need a WashDoc tab and their own resource checks. A failed read never becomes a successful empty result.