GET /events/v3/events with query params 'eventType' set to the fully qualified custom event name (e.g. pe{portalId}_{eventName}), 'occurredAfter' and 'occurredBefore' as ISO 8601 timestamps, and 'objectType'/'objectId' if filtering by a specific contact
Parse the 'results' array, extracting 'objectId', 'occurredAt', and the 'properties' map for each event occurrence
Use the 'paging.next.after' cursor from the response to fetch subsequent pages until no next cursor is returned
Aggregate event counts or property values in application code for reporting or segmentation purposes
Correlate objectId values against contact IDs retrieved from the CRM Contacts API to build a unified activity timeline
Known gotchas
Custom behavioral event names in the Events API are prefixed with the portal ID (pe{portalId}_); using the short name without the prefix returns no results without an error
The Events API v3 has a maximum lookback window — queries spanning more than 30 days may be rejected or return incomplete results depending on the account tier
Event properties are returned as string values regardless of the property type defined in the event schema; numeric and boolean values must be parsed by the caller
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp