Fires when an admin user saves the first status of a new claim. This is the event of the "Claim Submitted" admin alert. It fires where that alert is sent, also when the alert's email list is empty. It does not fire for agent users, which have the "Agent Claim Submitted" alert, or for a Historical status. status is the first status of the claim. revision_id is the policy revision in force on the loss date, which the alert routes by (policy type and state).
Field
Value
Topic
claims.claim_submitted_by_admin
Schema ID
BritecoreClaimSubmittedByAdmin.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_submitted_by_admin.json", "title": "ClaimSubmittedByAdminEvent", "description": "Fires when an admin user saves the first status of a new claim. This is the event of the \"Claim Submitted\" admin alert. It fires where that alert is sent, also when the alert's email list is empty. It does not fire for agent users, which have the \"Agent Claim Submitted\" alert, or for a Historical status. ``status`` is the first status of the claim. ``revision_id`` is the policy revision in force on the loss date, 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": "BritecoreClaimSubmittedByAdmin.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": "string" }, "status": { "type": "string" } }, "required": [ "claim_id", "claim_number", "policy_id", "revision_id", "status" ] } }, "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_submitted_by_admin.json
on the published portal.