Webhooks & events
How OmniValVMS receives partner callbacks today, and how client-facing event delivery will evolve.
OmniValVMS already processes inbound webhooks from appraisal ecosystem partners such as UCDP, VL Connect, WallE, CrossCheck Edge, and Mortgage Cadence. These callbacks update order workflow, submission status, documents, and exceptions inside the platform.
These are partner/system integration handlers, not a self-service client webhook API. Do not build client integrations that post directly to these handlers unless OmniValVMS has explicitly provisioned that partner integration for your organization.
Today, the public API reference exposes the partner webhook handlers OmniValVMS uses to receive partner events. A self-service developer portal where clients can register outbound webhook URLs, signing secrets, retry policies, and event subscriptions is planned, but not available yet.
Current webhook surface
Event types and workflow events
Events drive automation rules, comments, exceptions, and downstream order actions. Use the event type and workflow endpoints when you need to inspect the configured vocabulary that powers those flows.
| Action | Endpoint |
|---|---|
| List event types | |
| Get an event type | |
| List workflow events | |
| List event-based workflow actions |
Operational expectations
Webhook processing must be treated like any other order workflow automation:
- Idempotent handling — duplicate partner callbacks should not create duplicate documents, duplicate status changes, or duplicate payments.
- Recoverable failures — if a callback cannot be processed, operations needs enough context to retry or manually reconcile the order.
- Auditability — status changes, comments, exceptions, report updates, and submission results need to be visible in order history or workflow audit logs.
- No silent failures — failed partner events should be logged with partner, order, client, and correlation context where available.
Webhooks may trigger workflow actions, but the order's observable timeline is still the order history and audit trail. When investigating an event, start with the order history, then inspect workflow audit logs for automation detail.
Dashboard events
For client users, dashboard events are exposed separately from partner webhook ingestion:
These events support portal updates; they are not a replacement for a client-configurable webhook subscription system.