tickets/list-tickets returns every ticket attached to a post, from every active provider, with its price, sale window and complete capacity position.
Capacity is reported in full rather than flattened to one number, because in Event Tickets it genuinely is not one number.
At a glance
| Ability | tickets/list-tickets |
| Toolset | Event Tickets — toolset/event-tickets |
| Group | Event Tickets › Tickets |
| 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
A ticket can keep its own stock, draw from a shared event pool, draw from that pool up to a cap of its own, or be unlimited. Those are the four modes — own, global, capped and unlimited — and they behave differently enough that collapsing them loses the answer.
So every ticket comes back with its mode alongside its numbers: capacity, sold, pending and available. Pending matters more than people expect — a seat in somebody’s unpaid order is not available, and not yet sold.
A ticket in global or capped mode has no meaningful capacity of its own. For those, tickets/get-capacity-report is the call that answers “how many seats are left”.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
post_id | integer | Yes | The event, page or other ticketed post. |
What comes back
| Name | Type | What it is |
|---|---|---|
tickets | array | One entry per ticket: name, price, provider, sale window, capacity, mode, stock, sold, pending and available. |
count | integer | How many tickets the post has. |
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:
What tickets does this event have, and how many are left?
It resolves to one call:
{
"ability": "tickets/list-tickets",
"parameters": {
"post_id": 412
}
}Worth knowing
- Covers every active provider — RSVP, Tickets Commerce, and the WooCommerce or EDD providers where Event Tickets Plus is present.
- Pending is not sold and not available. Unpaid orders hold seats.
- For shared-pool tickets, read
tickets/get-capacity-reportinstead of doing arithmetic on these numbers.
Related abilities
- Get Capacity Report — the shared pool these may draw from
- Get Attendee Summary — how many people are actually coming
- Get Ticket — one ticket in full
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category