# Events
Klarefi event names and webhook delivery guidance for intake integrations
Source: https://www.klarefi.com/docs/reference/events

## Event model

Events are versioned integration signals. Use them to wake up your system, then
read the canonical session or case state when you need current data.

## Common events

- `v1.intake.session_created`
- `v1.intake.session_expired`
- `v1.intake.submitted`
- `v1.case.processing`
- `v1.case.applicant_blocked`
- `v1.case.needs_review`
- `v1.case.completed`
- `v1.case.failed`
- `v1.review.completed`
- `v1.document.processed`
- `v1.document.failed`
- `v1.intake.gap_resolved` - emitted when a missing information request is resolved
- `v1.fact.evidence_updated`
- `v1.webhook.delivery_failed`

`fact.review_completed` maps to catalog event `v1.review.completed` for
historical compatibility. Webhook payloads still carry the fact event stem in
`semantic_event_type`.

`v1.webhook.test` is reserved for the webhook test endpoint and is not a
subscription event.

## Delivery guidance

Process duplicate deliveries idempotently using `delivery_id`. Use `trace_id`
to correlate webhook delivery logs with your own receiver logs.