TicketSauce StrawberryEvents, event details and orders, worked for you
Hand a companion the outcome. It reads the TicketSauce events, does the 5-operation version of the job, and stops for your click on anything that changes a record.
Open the event. Check it against something else. Write the change. Move to the next one. That is the TicketSauce afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing changed until you say so.
What it can do is exactly what TicketSauce exposes to an account you authorise and nothing beyond it: 5 operations, 5 reads and no writes. In practice that means it can get ticket check-in ids, get orders and get order details, and work across the events, event details and orders.
The TicketSauce API stops at TicketSauce. A companion does not. The same run opens the customer's website, the supplier portal, the internal tool somebody built in 2019, because it is working the browser you are already signed into rather than calling in from outside it.
Which TicketSauce events does a companion see?
All 5 operations read.
Your account, not a guess at it: a companion can get ticket check-in ids, get orders and get order details, and the full list below is the whole list, with nothing inferred from TicketSauce's documentation.
The events are what most of this inventory is about, alongside the event details. A companion can hold all 5 of these operations and forty open tabs in the same pass, which is how an afternoon of TicketSauce admin becomes a queue you review.
- Get Ticket Check-in IDs
- Get Orders
- Get Order Details
- Get Events
- Get Event Details
Nothing writes back. So what moves the events?
Through the screens you already use.
TicketSauce exposes no write operation to a connected account, so a companion drives TicketSauce in the session you are already signed into instead, filling the same forms you would to move a event, and anything consequential stops for an approval card before it happens.
That is the ordinary case rather than the exception. Most of what an event in TicketSauce touches has no API pointed at it, and a companion is useful precisely because it does not need one.
Can it get ticket check-in ids every morning by itself?
Yes.
Saved as a routine, the TicketSauce events pass runs at the hour you pick: the Monday sweep, the overnight refresh, the Friday check. Keep Awake holds the machine awake for the length of a run, so a scheduled pass finishes with the lid closed.
The operations playbook catalogues the other recurring shapes of store admin, the TicketSauce events sweep among them, and finished runs are published at real runs.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents