This is the ability that answers “how many seats are left”, and it exists because reading a single ticket cannot answer it.
tickets/get-capacity-report reports the event-level shared pool alongside every ticket, so the relationship between them is visible.
At a glance
| Ability | tickets/get-capacity-report |
| Toolset | Event Tickets — toolset/event-tickets |
| Group | Event Tickets › Capacity |
| 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 in global or capped mode draws from the event pool rather than holding stock of its own. Three such tickets showing “40 available” each do not mean 120 seats — they may mean 40, shared.
capped is the subtle one: the ticket draws from the pool, but never more than its own limit. So its availability is the smaller of two numbers, and only one of them lives on the ticket.
Run this before publishing anything about availability, and before changing a capacity. It is the only view that makes overselling obvious in advance.
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 |
|---|---|---|
capacity | object | The shared pool and its remaining seats, plus every ticket with capacity, mode, stock, sold, pending and available. |
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:
How many places are actually left on this event across all its ticket types?
It resolves to one call:
{
"ability": "tickets/get-capacity-report",
"parameters": {
"post_id": 412
}
}Worth knowing
- Do not add up per-ticket availability on an event with a shared pool. That is the arithmetic this ability exists to prevent.
- Pending seats are held by unpaid orders. They are neither sold nor available.
- Read this before
tickets/set-ticket-capacityso the new number is chosen against reality.
Related abilities
- Set Ticket Capacity — change a ticket’s share
- List Tickets — the per-ticket view
- Get Attendee Summary — how many are actually coming
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category