Skip to main content
An event (a claim or an incident) closes and re-opens through two dedicated action endpoints, not through the generic entity update: Each moves eventStatus, stamps or clears the event’s Close Date, and appends an entry to the event’s open/close-history log — in one transaction. Close requires event.close; re-open requires event.reopen.

​
Why the status has its own endpoints

The status does not travel alone. The lifecycle dates a claim reports — opened on, previously closed on, re-opened on — are derived from the open/close-history log, so a status change that skipped the log would silently misreport them. eventStatus is therefore a system managed field: a value you send for it on a generic create or PATCH to /entities/event/{entityId} is silently ignored, leaving the stored value unchanged — see Flow-written status fields for how this interacts with the generic entity surface. To load a claim that was already closed, a historical import supplies the event’s eventOpenCloseHistory rather than its status — on create, or through PUT /events/{eventId}/open-close-history. The platform derives the status and close date from the log’s last entry, so the two can never disagree.

​
The effective date

Both endpoints take one required input, effectiveOnDate — the date the action takes effect, which may be earlier than today (typically the day the adjuster closed or re-opened the file). The date you acted is recorded separately by the platform and is not settable. It is an ordinary Date value: { "date": "2026-08-15", "timezone": "America/New_York" }. timezone may be omitted and defaults to America/New_York. The log cannot run backwards. effectiveOnDate must be on or after the last entry already in the event’s log; an earlier date returns 409 (EventLifecycleDateOutOfOrder), and the message names the date it has to clear. The same day as the previous entry is allowed. In practice this means an event cannot be closed before the day it was opened, or re-opened before the close it reverses.

​
Endpoints

  • Close Event — status becomes closed, Close Date is stamped with the date you send, and a close entry is appended to the log.
  • Re-open Event — status returns to open, Close Date is cleared, and a reopen entry is appended. The log entry is what preserves the previous close date: it is what a claim’s “previously closed on” is read from.
  • Replace Event Open/Close History (PUT /events/{eventId}/open-close-history) — replaces the whole log in one call, for historical imports and corrections. The status and close date are re-derived from the log’s last entry.