Fires when a loss report or a photo is uploaded to a claim or deleted from it. This is the event of the "Loss Report/Photos Uploaded or Deleted" admin alert. It fires where that alert is sent, also when the alert's email list is empty. action is "uploaded" or "deleted", and file_kind is "document" or "photo". A photo upload fires one time for each upload, with the first photo in file_id and file_title. revision_id is the claim's revision, which the alert routes by (policy type and state).
Field
Value
Topic
claims.claim_loss_report_updated
Schema ID
BritecoreClaimLossReportUpdated.v1
Version
1.0.0
Payload schema
Code
{ "$schema": "https://json-schema.org/draft/2020-12/schema", "$id": "https://docs.britecore.com/schemas/events/claim_loss_report_updated.json", "title": "ClaimLossReportUpdatedEvent", "description": "Fires when a loss report or a photo is uploaded to a claim or deleted from it. This is the event of the \"Loss Report/Photos Uploaded or Deleted\" admin alert. It fires where that alert is sent, also when the alert's email list is empty. ``action`` is \"uploaded\" or \"deleted\", and ``file_kind`` is \"document\" or \"photo\". A photo upload fires one time for each upload, with the first photo in ``file_id`` and ``file_title``. ``revision_id`` is the claim's revision, which the alert routes by (policy type and state).", "type": "object", "properties": { "event_id": { "type": "string", "format": "uuid", "description": "Unique identifier for this event instance." }, "event_date": { "type": "string", "format": "date-time", "description": "Timestamp the event was emitted (UTC)." }, "schema_id": { "type": "string", "description": "Schema identifier. Stable per event type.", "const": "BritecoreClaimLossReportUpdated.v1" }, "version": { "type": "string", "description": "Schema version.", "const": "1.0.0" }, "topic": { "type": "string", "description": "Topic the event was published on." }, "triggering_user": { "type": "object", "description": "User that triggered the event.", "properties": { "id": { "type": "string" }, "external_system_reference": { "type": "string" } } }, "data": { "type": "object", "properties": { "claim_id": { "type": "integer" }, "claim_number": { "type": "string" }, "policy_id": { "type": "integer" }, "revision_id": { "type": "integer" }, "action": { "type": "string" }, "file_kind": { "type": "string" }, "file_id": { "type": "string" }, "file_title": { "type": "string" } }, "required": [ "claim_id", "claim_number", "policy_id", "revision_id", "action", "file_kind", "file_id", "file_title" ] } }, "required": [ "event_id", "event_date", "schema_id", "version", "topic", "data" ]}
The schema is also published as a standalone JSON Schema artefact you can
fetch and consume programmatically. See schemas/events/claim_loss_report_updated.json
on the published portal.