In this section, object is short for bookable object: these can be seats that are part of a row, seats at a table, booths or general admission areas.
In Seats.io, objects can have one of three statuses for an event:
Initially, all objects start in status
Suppose then that you've enabled
session when rendering a chart. In that case, as soon as the ticket buyer clicks on a seat, it goes to status
reservedByToken. Note that this is a legacy status name: in the past, holding an object was known as reserving an object. We kept the status
reservedByToken to not break existing integrations.
reservedByToken means that the object is temporarily 'locked' so that only the person that originally held it can confirm the booking through a secret hold token. If no booking arrives within 15 minutes (by default) of holding the objects, seats.io automatically releases the held objects again.
The exact meaning of a
booked seat depends on your sales process, but this would typically be right before the payment gets processed. An object can go from
booked directly, or from
booked. That's up to you.
There are API calls to
/release seats, and also to hold them if you prefer to do that yourself instead of relying on the chart renderer parameter
session. You can also assign other, custom statuses. Say you want to create a separate status 'VIP', which indicates that a seat can only be booked by people that are logged in on your site as VIP. That's where /changeStatus comes into place.