What’s New
Property activity on the Partner API person object
GET /api/partner/people and GET /api/partner/people/:id now include two new fields on every person:
registrationPropertyActivity— the oldest property-related event tied to the lead (typically the listing they registered on).mostRecentPropertyActivity— the newest property-related event tied to the lead.
Each object includes eventId, eventType, occurredAt, propertyData (mlsNumber, address, price, bedrooms, bathrooms, etc.), and propertySearch when an active search is attached. Both fields are omitted when the person has no property events. Smart-list people responses and the Zapier/Make peopleCreated webhook payloads carry the same shape.
New property-specific webhook events
Three new Make.com and Zapier triggers, in addition to the existing eventsCreated stream:
propertyViewed— lead viewed a listing.propertySaved— lead saved/favorited a listing.propertyInquiry— lead submitted a tour request or property inquiry.
Subscribe to these for per-activity Zaps instead of filtering inside Zapier.
Behavior changes (read this if you have user-scoped webhooks)
User-scoped webhooks subscribed to eventsCreated, eventsUpdated, or eventsDeleted are now filtered by the user’s person-access scope. Previously these events were allow-by-default and could deliver activity for people outside the user’s pond/assignment scope. If a user-scoped webhook stops receiving an event you used to see, the user’s access to that person should be reviewed; team-scoped webhooks are unaffected.
Response size
The two new property-activity objects add to the size of /api/partner/people list responses for property-active books of business. Fields are omitted entirely when the person has no property events, so leads without property activity are unaffected.