Data New Webhook

The DATA_NEW webhook is sent whenever a new record is created in Propexo for one of your subscribed objects. This allows your system to react immediately to new entities without polling the Propexo API. A common use case is when customers are creating new records in Propexo and want to automatically pull those new records into their own system after creation. It can also be used in sequence with the DATA_UPDATE webhook for additional data hydration. For more details, please see the ‘Sequencing and Data Hydration’ article.
Please note that the DATA_NEW webhook is not sent for first syncs and backsyncs.

When It Triggers

A DATA_NEW webhook is triggered whenever a subscribed object is created within Propexo. Examples include:

• A new resident record is added.
• A new applicant is submitted.
• A new lease is created.

Common Use Cases

• Triggering workflows such as notifications, onboarding processes, or downstream integrations.

Special Considerations

Some models have interdependencies. For example, you may receive separate DATA_NEW 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.

Example Payload showing a new event on Entrata:

1
{
2
  "context": {
3
    "property_id": "property_id_redacted"
4
  },
5
  "event": "DATA_NEW",
6
  "integration_id": "integration_id_redacted",
7
  "job_id": "job_id_redacted",
8
  "job_type": "READ_LEAD_EVENTS",
9
  "meta": {
10
    "integration_id": "integration_id_redacted",
11
    "object": "events"
12
  },
13
  "object": "events",
14
  "payload": {
15
    "created_at": "2025-08-18T13:01:43.525Z",
16
    "event_name": "Email Opt-In",
17
    "notes": "Event Scheduler Email",
18
    "reasons_for_event": "redacted_reason"
19
  },
20
  "record_id": "record_id_redacted",
21
  "root_job_id": "root_job_id_redacted",
22
  "vendor": "ENTRATA"
23
}

Field Reference

• event (string) — The webhook event type. For this event, the value is DATA_NEW.
• object (string) — The data model affected (e.g., residents, applicants, leases).
• record_id (string) — The unique Propexo ID for the record (often includes integration and source IDs).
• payload (object) — The full details of the new record. The shape varies by model.