Retrieve the complete list of available webhook events you can subscribe to.

Event Categories:

People Events:

• peopleCreated - New contact created
• peopleUpdated - Contact details updated
• peopleDeleted - Contact deleted
• peopleTagsAdded - Tags added to contact
• peopleTagsRemoved - Tags removed from contact
• peopleStageUpdated - Contact pipeline stage changed
• peopleAssigned - Contact assigned to user/team
• peopleUnassigned - Contact unassigned

Company Events:

• companiesCreated - New company created
• companiesUpdated - Company details updated
• And more...

Communication Events:

• emailsCreated - Email sent or received
• callsCreated - Call logged
• textMessagesCreated - SMS sent or received
• notesCreated - Note added

Task & Activity Events:

• tasksCreated - Task created
• appointmentsCreated - Meeting/appointment scheduled

Contract Events:

• contractsCreated - New contract created
• contractsUpdated - Contract details updated
• contractsDeleted - Contract removed
• contractsStageUpdated - Contract stage changed
• contractPipelineStatusesCreated - Contract pipeline stage assigned
• contractPipelineStatusesUpdated - Contract pipeline stage changed
• contractPipelineStatusesDeleted - Contract pipeline stage removed

Property Activity Events (SUR-1665):

• propertyViewed - Lead viewed a property listing
• propertySaved - Lead saved/favorited a property
• propertyInquiry - Lead submitted a property inquiry

Note: Property activity events fire in addition to the generic
eventsCreated event for the same underlying Event row. Subscribe
selectively based on whether you want a unified stream or per-activity
triggers in your Zaps. Partners are responsible for MLS display
compliance in downstream systems.

Field naming: each webhook's data payload follows that payload's
existing convention. The generic event webhooks (eventsCreated,
eventsUpdated, eventsDeleted) use snake_case fields, so the
normalized event type is data.canonical_event_type there. The
property activity webhooks (propertyViewed, propertySaved) use
camelCase fields, so it is data.canonicalEventType there — matching
the REST responses. Both carry the same normalized value.

See the full response for all 40+ available events.