For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Dashboard
How It WorksKnowledge BaseOnboardingVideo TutorialsPMS GuidanceAPI ReferenceRelease Notes
  • Getting Started
    • Introduction
  • Propexo API Concepts
    • Authentication
    • Custom Data Objects
    • Data Fetching Methodology
    • Deleted Records
    • Enabling Properties
    • Filtering Results
    • Integration Cloning
    • Pagination
    • Rate Limiting
    • Records Processed
    • Sorting Results
    • Sync Frequency
    • Sync Schedules
    • Write Requests
  • Webhooks
    • Webhooks Overview
    • Setting Up Webhooks in Propexo
    • Sending a Test Webhook
    • Sequencing and Data Hydration
    • Signed Payloads
      • Completed Sync
      • First Sync Complete
      • Data New
      • Data Update
      • Job Failure
      • Write Operation Failure
Dashboard
LogoLogo
On this page
  • When It Triggers
  • Special Considerations
  • Common Use Cases
  • Example Payload showing an updated lead in Realpage App Partner:
  • Field Reference
WebhooksWebhook Details

Data Update Webhook

Was this page helpful?
Previous

Job Failure

Next
Built with

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:

1{
2 "context": {
3 "property_id": "property_id_redacted"
4 },
5 "diff": {
6 "new": {
7 "country": "United Sta",
8 "last_seen": "2025-08-18T13:06:56.283Z"
9 },
10 "previous": {
11 "country": "US",
12 "last_seen": "2025-08-13T12:56:41.009Z"
13 }
14 },
15 "event": "DATA_UPDATE",
16 "integration_id": "integration_id_redacted",
17 "job_id": "job_id_redacted",
18 "job_type": "READ_LEADS",
19 "meta": {
20 "integration_id": "integration_id_redacted",
21 "object": "leads"
22 },
23 "object": "leads",
24 "record_id": "record_id_redacted",
25 "root_job_id": "root_job_id_redacted",
26 "vendor": "REALPAGE_RPX"
27}

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.