Error history
—Explore a bank’s machine errors by period and severity. Read the event details or acknowledge an error after review. Acknowledgement keeps the log and does not change the machine’s status.
Connect and choose a bank, or try the demo.
Error events will appear here.
API operations and limitations
POST /api/v1/session/loginandPOST /api/v1/session/renew— shared bearer login.GET /api/v1/search/banks?q=example— choose a bank without requiring Banks2.GET /api/v1/banks/{bankKid}/errors?days=10&level=JAN&pageSize=50— cursor-paged history.GET /api/v1/errors/{errorKid}— stored details, including acknowledgement status.POST /api/v1/errors/{errorKid}/acknowledgewith{"expectedRevision":"revision from event"}.
Read access requires Errors2 (17), Bank/Location/Unit Read and matching grants. Acknowledgement additionally requires Unit Write and fresh authorization. All events within 1–70 days can be paged; the legacy four-per-machine limit does not apply. Results are ordered by location, machine and newest event, then source.
Descriptions come from the stored event. The obsolete DatPro2 error-description catalogue and its editor are not exposed. Structured details expose only the error code, Miele count and Miele/Electrolux text. Missing data stays unknown. Current machine type uses only the original packed UnitType. Print is a local, read-only view of the selected detail.
Acknowledgement writes Period=1 and preserves the original event. It does not repair or restore the machine. A 409 response requires a fresh read. If a write response is lost, read the event again before deciding whether to retry. This example never retries a POST automatically.