What this person actually did, newest first, to the microsecond.
Where the profile’s touchpoints say where a person appears, this says how they behaved: opens, link clicks, scheduling-page views, bookings, calls and sequence status changes, merged into one time-ordered stream.
Currently covers sequence engagement. Marketing campaigns record only first/last open and click counters rather than individual events, and the website pixel keeps one row per person rather than one per visit, so neither can contribute a real event stream yet.
Events attributed to scanners and mail-proxy prefetchers (Microsoft Safe
Links, GoogleImageProxy) are excluded by default — they are not human
actions, and counting them would overstate engagement. botCount reports
how many were held back; pass includeBots=true to see them, each flagged
with isBot and the provider that was identified.
Authorizations
Company API key - scoped to a specific company. Generate from the Integrations page in your dashboard.
Path Parameters
Query Parameters
Company ID. Required for PAK/API key auth; optional for JWT auth.
1-indexed page number
Events per page. Default 50, max 200.
Comma-separated event types to include. Any of: open, click, schedule_view, schedule_booking, status_change, voice_call_completed. Omit for all.
Include events attributed to scanners and mail-proxy prefetchers (Microsoft Safe Links, GoogleImageProxy, etc.). Excluded by default because they are not human actions.
Response
Paginated engagement timeline for one person
Paginated person activity timeline
Bot events excluded from (or included in) this filter set
Events, newest first
Current page
Events per page
Total events matching the current filters
True when the person has more events than one scan covers, so older history is omitted

