By InsuranceFlow Editorial · November 1, 2026
An integration design should distinguish the time an event occurred from the time it was received. Preserve source identifiers, normalize statuses explicitly, and design consumers to tolerate duplicate delivery. For an agency user, the useful result is a readable update attached to the right application. For an integration team, it means keeping original source values alongside normalized statuses and checking the permitted tenant, case, and carrier before a change. A transport response is not an insurance decision: receiving an HTTP success response does not mean a carrier accepted evidence. RFC 9110 describes HTTP method and response semantics; the insurance workflow still needs its own explicit acceptance event. These are design principles, not a claim that a production connector is available.