swarmtix_orders_list

Lists the orders placed for one event, newest first, one page at a time. Each entry carries the order id, the buyer's name, the number of tickets, the total paid with the event's currency code, when it was placed, how the order was taken, and whether it is still active.

When you would reach for it

• To see recent sales without opening the dashboard.
• To find an order id for swarmtix_orders_get.
• To read the answers buyers gave to your checkout questions, which ride along on each order.

Scope

orders:read

This scope exposes your buyers' personal details by design. Each order carries the buyer's name, and the all-dates listing also carries their email address. The consent page says so in those words before you approve it.

Ticket barcodes and security codes are never returned, by this tool or any other.

Parameters

Example call

{
  "name": "swarmtix_orders_list",
  "arguments": { "event": "spring-summit-2026", "limit": 2 }
}

What comes back

[
  {
    "orderId": 184149,
    "eventId": "8f14e45f-ceea-467a-9c3d-1b2a5f6e7d80",
    "buyerName": "Sarah Meyer",
    "buyerEmail": "[email protected]",
    "ticketCount": 2,
    "totalAmount": 91.7,
    "currency": "EUR",
    "currencySymbol": "€",
    "placedAt": "2026-10-28T14:22:09",
    "active": true,
    "orderType": "online",
    "checkoutAnswers": "Any dietary requirements: Vegetarian"
  },
  {
    "orderId": 184148,
    "eventId": "8f14e45f-ceea-467a-9c3d-1b2a5f6e7d80",
    "buyerName": "Tomás Ribeiro",
    "buyerEmail": "[email protected]",
    "ticketCount": 1,
    "totalAmount": 46.35,
    "currency": "EUR",
    "currencySymbol": "€",
    "placedAt": "2026-10-28T11:04:51",
    "active": true,
    "orderType": "door"
  }
]

Showing 2 of 312. Call again with cursor "MDAwMmNmNTUtMDAwMC0wMDAwLTAwMDAtMDAwMDAwMDAwMDAw" for the rest.

currency and currencySymbol are two fields on purpose. The code is what identifies the currency — "$" is four different ones, so totalling figures across events on the symbol is not safe. The symbol is there for rendering a number to a reader and nothing else.

orderType is a word, not a number:

checkoutAnswers can contain whatever a buyer typed into a custom question. Treat it as personal data.

What happens when you call it

1. The event identifier is resolved and the ownership checks run.
2. limit is checked, and eventDate is parsed if given. An eventDate that is not an id is refused rather than ignored — treating it as "all dates" would answer a wider question than you asked with a number that looks like the answer to yours.
3. Every order for the event — or for that one date — is fetched in one unbounded list.
4. The list is sorted newest first, with the order id breaking ties between orders placed in the same instant.
5. One page is cut, projected to the fields above, and serialized.

Troubleshooting

buyerEmail is missing from every row

You passed eventDate. Remove it and list across all dates, or read the order with swarmtix_orders_get.

"eventDate is not valid: it is not an id. Expected an event date id (a GUID) from the event dates tool, or nothing for every date."

eventDate must be a date id from swarmtix_event_dates_list, not a calendar date like 2026-11-04.

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

The event does not exist, or it belongs to a different organisation than this connection covers.

"cursor is not valid: the order it points at is no longer in this list."

The order named by the cursor is no longer in the result set — often because it was cancelled, or because a different eventDate was passed on the second call. Keep the arguments identical between pages, or start again.

"This connection is not authorized for orders:read. Reconnect and grant it to use this tool."

Reconnect and approve orders:read. Bear in mind what it grants: your buyers' names and email addresses. If you only want sales figures, analytics:read answers most of those questions without any personal data — see swarmtix_analytics_event.

The list is longer than one page

That is normal, and it is not an error. Pass the cursor from the continuation line back as cursor, or narrow the question to one date.

Use cases

• "What sold today?" — the newest orders are first, so the first page is the answer
• Support lookups — find an order by buyer name, then read it in full
• Dietary and accessibility rollups — checkoutAnswers across a page of orders
• Reconciliation — order totals against the revenue on swarmtix_analytics_event