Read-only.
When to use it
- “Show me every event anyone from these 30 target accounts has been to.”
- “Which of these people actually checked in, and where?”
- “Give me the LA dinner roster as a CSV with partner source and city.”
- “Who from Wavecrest has registered for anything this quarter?”
Parameters
Give at least one ofdomains, emails or channel_id.
Response
data[0] holds the page of rows and counts over the whole matching set.
How to read
status:
attendedis a checked-in sign-up.registeredis an RSVP, never attendance.no_showappears only for a held event whose source recorded check-in. Where check-in was not recorded the sign-up readsregisteredwith apartial_coveragegap.- An event not yet held reads
registeredwith a gap. seniorityis advisory, from the title, and used by no rule or count.- A null
partner_sourcedoes not mean no partner brought the person.
Rules the agent must follow
- Registered is not attended. Only
attended(checked in) means the person came. - Null is unknown, never zero.
- Nothing here is a ranking or engagement metric. Do not grade people from it.
- Page with
next_cursoron the same filters; do not fan out per-event get_event_details calls instead. - No row reads
cancelledtoday, because no store records a cancelled registration.
Errors and gaps
invalid_parameter: none ofdomains,emailsandchannel_idwas given, or a filter, limit or cursor is malformed.partial_coveragegap: an event not yet held, or check-in not recorded. Not retryable. Disclose it.entitlement_required: the plan lacks MCP read.internal_error: retry once.
Related
- get_account_relationship: one account, contacts collapsed to their most recent event.
- get_event_details: one event’s roster and attendance mix.
- check_people: what the workspace knows per email, before an import.
- Playbook: Did anyone follow up, and what did the event do for pipeline.