Webhook Events

Every event shares the same envelope. Each event type has its own page covering what goes in data, when it fires, and — just as importantly — the cases where it is deliberately not sent.

Read the Webhooks guide first for signature verification, retries, and idempotency.

New event types are added over time and are opt-in per subscription. Route on eventType and ignore values you do not recognize; a subscription only receives the events it was provisioned for.

Available

Delivered today. Subscribe and build against these.

Event	Fires when
`prospect.created`	A new prospect record is created in Fortress
`message.received`	A new inbound message is received
`application.completed`	An application’s status moves to APPROVED, CANCELED, DENIED, ABANDONED or WAITLIST
`application.signed`	Each time the last required adult in a household e-signs their application form
`requirement.upload_received`	A document is uploaded to a requirement
`requirement.upload_removed`	A document is removed from a requirement
`agent.state_changed`	Staff enable or disable an agent (`cora` or `leslie`) for a property (`scope` `PROPERTY`), or change the CORA cadence policy of a property
`compliance_review.opened`	Staff open a manual compliance review on an application
`compliance_review.closed`	Staff close the manual compliance review on an application

Every requirement.* event describes one requirement; they fire for DOCUMENT slots only.

Defined, not yet delivered

Documented so that you can build and test your receiver with the trigger. Real deliveries start when the publisher ships. Subscriptions may list these event types today.

Event	Fires when
`subscription.created`	A resident subscription starts
`subscription.updated`	A resident subscription changes plan or status
`subscription.ended`	A resident subscription ends
`customer.updated`	A customer with a live subscription changes a watched field
`lease.updated`	The lease of a household with a live subscription changes a watched field