tickets/set-ticket-capacity changes capacity and mode without touching name, price or sale window.
It exists as a separate ability because capacity is the field most likely to be got wrong, and getting it wrong means selling seats that do not exist.
At a glance
| Ability | tickets/set-ticket-capacity |
| Toolset | Event Tickets — toolset/event-tickets |
| Group | Event Tickets › Capacity |
| Requires | Event Tickets, active on the site |
| Capability | manage_options |
| Safety | Writes data |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Abilities Manager 0.0.34 and later |
The reconciliation is the point
Stock in Event Tickets is what remains, not what was originally offered. Write the meta directly to 100 on a ticket that has sold 30 and the plugin now believes 130 seats exist.
This routes through the plugin’s own capacity handling, which subtracts sold and pending from the new number — so setting 100 on that ticket leaves 70 in stock and 100 total, which is what anybody actually meant.
The result is read back and the call is refused if it did not take. A capacity write that silently failed is indistinguishable from one that worked until the event oversells.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
ticket_id | integer | Yes | The ticket ID. |
capacity | integer | No | New capacity. -1 for unlimited. |
capacity_mode | string | No | own keeps independent stock; global draws from the event pool; capped draws from the pool up to a limit; unlimited has no cap. |
shared_cap | integer | No | The limit when the mode is capped. |
What comes back
| Name | Type | What it is |
|---|---|---|
ticket | object | The ticket after the write, read back from the plugin. |
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:
We’ve got a bigger room — raise this ticket from 50 to 80.
It resolves to one call:
{
"ability": "tickets/set-ticket-capacity",
"parameters": {
"ticket_id": 980,
"capacity": 80
}
}Worth knowing
- Idempotent — setting the capacity it already has changes nothing.
- Never write
_tribe_ticket_capacityor its siblings directly. This is the only safe route. - Reducing capacity below what is already sold is a decision, not an error. Read
tickets/get-capacity-reportfirst.
Related abilities
- Get Capacity Report — the picture before you change it
- Get Ticket — the ticket’s current mode
- Update Ticket — change other fields too
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category