Fires when a Straight Through Processing (STP) result is sent to underwriting. This is the event of the "Straight Through Processing results" admin alert. It fires at each point that sends that alert, also when the alert's email list is empty. result tells which point: * "issued": STP approved the submission and the policy was issued. * "referred": STP did not approve the submission, so it waits for an underwriter. * "renewal_referred": STP did not approve an automatic renewal, so the renewal stays open for an underwriter. * "review_requested": the agent requested an underwriter review. * "review_approved": the underwriter approved the review. * "review_declined": the underwriter declined the review. revision_id is the revision the alert routes by (policy type and state). stp_details is the list of STP rule results, when the point has one.
Field
Value
Topic
quotes.stp_result_generated
Schema ID
BritecoreStpResultGenerated.v1
Version
1.0.0
Payload schema
Code
{ "$schema": "https://json-schema.org/draft/2020-12/schema", "$id": "https://docs.britecore.com/schemas/events/stp_result_generated.json", "title": "StpResultGeneratedEvent", "description": "Fires when a Straight Through Processing (STP) result is sent to underwriting. This is the event of the \"Straight Through Processing results\" admin alert. It fires at each point that sends that alert, also when the alert's email list is empty. ``result`` tells which point: * \"issued\": STP approved the submission and the policy was issued. * \"referred\": STP did not approve the submission, so it waits for an underwriter. * \"renewal_referred\": STP did not approve an automatic renewal, so the renewal stays open for an underwriter. * \"review_requested\": the agent requested an underwriter review. * \"review_approved\": the underwriter approved the review. * \"review_declined\": the underwriter declined the review. ``revision_id`` is the revision the alert routes by (policy type and state). ``stp_details`` is the list of STP rule results, when the point has one.", "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": "BritecoreStpResultGenerated.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": { "policy_id": { "type": "integer" }, "revision_id": { "type": "integer" }, "policy_term_id": { "type": "integer" }, "quote_external_system_reference": { "type": "string" }, "result": { "type": "string" }, "stp_details": { "type": "string" } }, "required": [ "policy_id", "revision_id", "policy_term_id", "quote_external_system_reference", "result", "stp_details" ] } }, "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/stp_result_generated.json
on the published portal.
