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
Dashboard
LogoLogo
On this page
  • Why Sequencing Happens
  • Example Scenario
  • Handling Sequencing in Your Implementation
Webhooks

Sequencing & Data Hydration

Was this page helpful?
Previous

Signed Payloads

Next
Built with

In some integrations, Propexo delivers data in multiple stages rather than in a single, complete payload. This process — known as sequencing and data hydration — ensures you receive initial information as soon as possible, followed by additional details as they are retrieved from the connected property management system (PMS).

Why Sequencing Happens

Many PMS integrations initially return only a minimal dataset for certain models such as residents, applicants, or leads. This might contain just an ID and a name. Propexo then makes one or more subsequent requests to retrieve the full dataset, which can include fields like phone numbers, email addresses, and other attributes.

Because of this, a single record may trigger multiple webhook events — an initial one with partial data, and one or more follow-ups containing the full set of fields.

Example Scenario

  1. A new resident is added to the PMS.
  2. Propexo sends a DATA_NEW webhook with only the resident’s ID and name.
  3. Propexo retrieves additional details such as phone numbers and email addresses.
  4. A DATA_UPDATE webhook is sent, adding these enriched details to the record.

Handling Sequencing in Your Implementation

To ensure you receive and process complete records, consider the following approaches:

  • Subscribe to DATA_NEW only – Suitable if the initial minimal data is enough for your use case.
  • Subscribe to both DATA_NEW and DATA_UPDATE – Ensures you capture both the initial creation and any additional details retrieved later.
  • Use webhooks as triggers for API calls – Many customers treat webhooks as notifications, then call the associated API endpoint to retrieve the most up-to-date record. Example: Subscribe to DATA_UPDATE for the leases model. When you receive an update webhook, call /leases/:id to fetch the full lease record.