Data Update Webhook
The DATA_UPDATE webhook is sent whenever an existing record in Propexo is updated. This allows your system to stay synchronized with changes as they happen in connected property management systems. It can also be used in sequence with the DATA_NEW webhook for faster data hydration. For more details, please see the ‘Sequencing and Data Hydration’ article. Please note that the DATA_UPDATE webhook is not sent for first syncs and backsyncs.
When It Triggers
A DATA_UPDATE webhook is triggered when any field in a subscribed object changes. Common scenarios include:
- A lease status changes (e.g., from “active” to “terminated”).
- A resident’s contact information is updated.
- A unit’s attributes (e.g., rent amount) are modified.
Special Considerations
Some models have interdependencies. For example, you may receive separate DATA_UPDATE events for a lease and a resident, but the payloads themselves will not indicate whether the resident is linked to that lease.
To determine these relationships, subscribe to the residents-to-leases model in addition to your primary object subscriptions.
Common Use Cases
- Triggering workflows for key changes, such as sending renewal notices when a lease end date changes.
Example Payload showing an updated lead in Realpage App Partner:
Field Reference
- event – The webhook event type.
- record_id – The unique ID for the record in Propexo.
- diff – An object showing both the previous and new values for the updated fields.

