tickets/list-attendees returns the attendee records for a post: which ticket, which order, checked in or not.
What it does not return by default is anything that identifies a person.
At a glance
| Ability | tickets/list-attendees |
| Toolset | Event Tickets — toolset/event-tickets |
| Group | Event Tickets › Attendees |
| Requires | Event Tickets, active on the site |
| Capability | manage_options |
| Safety | Read-only — changes nothing |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Abilities Manager 0.0.34 and later |
How it works
Names and email addresses come back only when include_personal_data is true, and the response reports how many records that disclosed. The flag exists because this data leaves the site the moment an assistant reads it, and that should be a decision rather than a default.
The check-in security code is never returned, with or without the flag. It is the credential printed on the ticket — disclosing it would let someone check in as another attendee, and there is no use case that justifies the risk.
Where the question is about numbers rather than people, tickets/get-attendee-summary answers it with no disclosure at all.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
post_id | integer | Yes | The event, page or other ticketed post. |
include_personal_data | boolean | No — defaults to false | Include names and email addresses. Off by default, because this data leaves the site when an assistant reads it. The response reports how many records were disclosed. |
page | integer | No — defaults to 1 | 1-based page number. |
per_page | integer | No — defaults to 20, max 100 | Results per page. |
What comes back
| Name | Type | What it is |
|---|---|---|
attendees | array | Ticket, order and check-in status per attendee. |
total | integer | How many attendees the post has. |
disclosed | integer | How many records had personal data returned. |
success | boolean | Whether the call completed. |
message | string | A one-line summary of what happened, suitable for showing a human. |
error_code | string | Present only on failure — a stable machine-readable reason, such as a missing field, a wrong field type or an unmet confirmation. |
Example
Ask your assistant:
List who’s attending this event — I need the names for the door.
It resolves to one call:
{
"ability": "tickets/list-attendees",
"parameters": {
"post_id": 412,
"include_personal_data": true,
"per_page": 100
}
}Worth knowing
- Default to
tickets/get-attendee-summary. Only list attendees when you need the individuals. - The
disclosedcount is there so a disclosure is on the record. Treat it as one. - The security code is never returned. Checking someone in is done by attendee ID through
tickets/check-in-attendee.
Related abilities
- Get Attendee Summary — the same question without disclosure
- Check In Attendee — mark one as arrived
- Get Order — the purchase behind an attendee
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category