Adds a ticket type to an event — the product definition buyers choose from, not a sold ticket

swarmtix_ticket_types_create

Adds a ticket type to an event and returns it. A ticket type is the product definition buyers choose from; creating one sells nothing and charges nobody.

When you would reach for it

Building out a new draft's tiers — general admission, early bird, student, workshop add-on.
Adding a tier to a live event that is selling faster than expected.
Creating a free ticket — a price of 0 does it.

Scope

events:write

Calling this twice adds two ticket types with the same name. It is not idempotent. If a call times out, check swarmtix_ticket_types_list before calling again.

Parameters

Name	Type	Required	Default	Description
`event`	string	Yes	—	The event's id (a GUID) or its URL slug.
`name`	string	Yes	—	The name buyers see, for example `"General Admission"`. Up to 500 characters.
`price`	number	Yes	—	The price of one ticket in the event's currency. `0` for a free ticket. Up to 1,000,000.
`quantity`	integer	Yes	—	How many of this ticket to put on sale. 1 to 1,000,000.
`description`	string	No	—	What this ticket includes, shown under its name. Up to 4,000 characters.
`minimumPerOrder`	integer	No	`1`	The smallest number of this ticket one order may contain.
`maximumPerOrder`	integer	No	`10`, or `quantity` if that is smaller	The largest number of this ticket one order may contain.

Both per-order limits must be between 1 and quantity, and the minimum must not exceed the maximum.

price is rounded to two decimal places. That is what keeps 19.99 from being stored as 19.989999999999998 and reported back with a fractional cent nobody typed.

The sale window is not a parameter

The ticket goes on sale as soon as the event itself is published and stops when the event starts — the same defaults the dashboard produces. Scheduling when money starts changing hands is a decision that stays with a person; set a custom window in the dashboard.

Example call

{
  "name": "swarmtix_ticket_types_create",
  "arguments": {
    "event": "spring-summit-2027",
    "name": "Early Bird",
    "price": 39.5,
    "quantity": 100,
    "description": "All talks and the evening reception. Limited to the first 100.",
    "maximumPerOrder": 4
  }
}

What comes back

The ticket type as stored:

{
  "id": "b7d3e5a1-92c4-4f18-8a6b-3e0f1c7d9a52",
  "eventId": "3b6f81ce-04a2-4d97-b5e8-7c10924af3d6",
  "name": "Early Bird",
  "description": "All talks and the evening reception. Limited to the first 100.",
  "price": 39.5,
  "free": false,
  "quantity": 100,
  "available": 100,
  "minimumPerOrder": 1,
  "maximumPerOrder": 4,
  "onSaleFrom": "2027-01-14T11:02:48",
  "onSaleUntil": "2027-11-03T19:00:00",
  "active": true
}

Field	What it is
`id`	The new ticket type's id
`eventId`	The event it was added to
`name`, `description`	As stored
`price`	The face price, rounded to two decimals
`free`	Whether this is a free ticket rather than a paid one
`quantity`	How many were put on sale
`available`	How many are still available — equal to `quantity` on a new type
`minimumPerOrder`, `maximumPerOrder`	The per-order limits
`onSaleFrom`	When sales open — set to the moment the ticket type was created
`onSaleUntil`	When sales close — taken from the event's earliest date. Absent when the event has no dates yet, and filled in once it has.
`active`	Whether the type is switched on

Creating ticket types before setting the schedule is fine and common; onSaleUntil simply stays empty until swarmtix_event_dates_set has run.

free is derived from the price rather than accepted as an argument. A price of 0 makes a free ticket; anything above makes a paid one. Keeping them in step is what stops a ticket priced at zero being reported as a paid one.

What happens when you call it

The event is resolved through the edit gate. The service behind this tool performs no authorization of its own, so that gate is the whole control.
Every argument is validated. The protocol layer publishes the schema and enforces none of it, so on a write path the schema is a suggestion until this step makes it a contract.
The ticket type is created against the event from the gate — never an event id taken from your arguments.
Its remaining availability is seeded from the quantity. Without that step a new ticket type would be on sale with nothing available.
The stored row is read back and returned.

Tiering a new event — general, early bird, student, in three calls
Free workshop add-on — price: 0
Group control — maximumPerOrder to stop one buyer taking the block
Late release — a second tier once the first sells out

swarmtix_ticket_types_create

swarmtix_ticket_types_create

When you would reach for it

Scope

Parameters

The sale window is not a parameter

Example call

What comes back

What happens when you call it

Troubleshooting

"`name` is not valid: it was empty. Expected the name buyers see for this ticket."

"`price` is not valid: it was -5. Expected an amount from 0 to 1000000."

"`quantity` is not valid: it was 0. Expected a whole number from 1 to 1000000."

"`maximumPerOrder` is not valid: it was 250. Expected a whole number from 1 to 100."

"`minimumPerOrder` is not valid: it is 5 and maximumPerOrder is 2. Expected a minimum no larger than the maximum."

"`description` is not valid: it is 5200 characters. Expected what this ticket includes, at most 4000 characters."

"Event not found, or this connection does not have access to it."

"This connection is not authorized for `events:write`. Reconnect and grant it to use this tool."

"Swarmtix could not complete this request. Nothing was changed."

Two identical ticket types now exist

The new type is not on sale yet

Use cases

On this page