swarmtix_ticket_types_reorder

Sets the order buyers see an event's ticket types in, and returns them in that order. Nothing but the order changes: no price, quantity or sale window is touched.

When you would reach for it

Putting the early bird first after adding a cheaper tier.
Moving the VIP tier to the end of the list.

Scope

events:write

It is idempotent: sending the same order twice leaves the same order, so a client may safely retry.

Parameters

Name	Type	Required	Default	Description
`event`	string	Yes	-	The event's id (a GUID) or its URL slug.
`ticketTypes`	string[]	Yes	-	The ids of all the event's active ticket types, each exactly once, in the order they should appear.

The list must name every active ticket type once. A missing, repeated or unknown id is refused, and nothing is changed. That keeps a partial list from leaving the other types in an order nobody chose.

Example call

{
  "name": "swarmtix_ticket_types_reorder",
  "arguments": {
    "event": "spring-summit-2027",
    "ticketTypes": [
      "b7d3e5a1-92c4-4f18-8a6b-3e0f1c7d9a52",
      "5e0a9c42-1f6d-4d0b-b7a3-2c8e41f7d6a9"
    ]
  }
}

What comes back

{
  "ticketTypes": [
    { "id": "b7d3e5a1-92c4-4f18-8a6b-3e0f1c7d9a52", "name": "Early Bird" },
    { "id": "5e0a9c42-1f6d-4d0b-b7a3-2c8e41f7d6a9", "name": "General Admission" }
  ]
}

Each entry is the full ticket type, in the shape swarmtix_ticket_types_create returns, in the new order.

Troubleshooting

"`ticketTypes` is not valid: it does not list every active ticket type of this event exactly once."

The message names how many ids it expected. List the ticket types with swarmtix_ticket_types_list and send all of them.

"`ticketTypes` is not valid: none were given."

The list was empty.

Use cases

Ordering tiers from cheapest to dearest
Moving a sold-out tier down the list

swarmtix_ticket_types_reorder

On this page