Changelog

Breaking or behavior-changing API updates are listed here, newest first. Additive changes (new fields, new endpoints) are not listed unless they change existing behavior.

2026-10-19: revision history can include start-of-inspection answers

GET /v1/inspections/{inspection_id}/corrections/{correction_id}/revisions and GET /v1/inspections/{inspection_id}/revisions accept include_start=true. With it, the history also lists changes to an inspection's start-of-inspection answers, merged in time order with the same cursor. Those items carry answer_source: "start", a group_key and an entry_index when the answer belongs to a repeating entry, and a field_id that is the start field's key rather than a UUID. Without the parameter the responses are unchanged, but the schema for field_id is now a plain string instead of a UUID string, so a client that validates the format should accept both.

2026-07-18: omitted scheduled_at creates an unscheduled inspection

Creating an inspection without scheduled_at (or with scheduled_at: null) now yields an UNSCHEDULED inspection: the stored date is null, the inspection has no due date, it is never counted or shown as overdue, and it produces no reminder notifications. Pass an explicit timestamp to schedule an inspection. Previously the creation instant was silently used as the scheduled date, which made every undated inspection appear overdue immediately.

Related behavior in the same release: an inspector self-create without a date starts the inspection immediately (in_progress, started_at stamped), and duplicated or follow-up inspections start unscheduled.