Skip to main content

General admission areas

Rate limits

This endpoint belongs to the priority lane.

To book general admission places (let's say 5), you can either:

  • pass in the label of the general admission area 5 times
  • or pass in the label of the general admission area and a quantity (e.g. 5)
Note

All GA places passed in to this API will be considered as "used seats" for pricing purposes.

POST https://api-{region}.seatsio.net/events/{eventKey}/actions/change-object-status
POST https://api-{region}.seatsio.net/events/{eventKey}/actions/book
POST https://api-{region}.seatsio.net/events/{eventKey}/actions/hold
POST https://api-{region}.seatsio.net/events/{eventKey}/actions/release

Request without quantity

{
"objects": ["GA1", "GA1", "GA1", "GA1", "GA1"],
"status": "booked"
}

Request with quantity

{
"objects": [{"objectId": "GA1", "quantity": 5}],
"status": "booked"
}

Temporarily holding places in a GA area

Holds for GA areas work in the same way as regular objects. Have a look at our documentation for more details.

Custom statuses

It's technically possible to use custom statuses on areas:

{
"objects": [{"objectId": "GA1", "quantity": 5}],
"status": "myCustomStatus"
}

However, Seats.io does not keep track of the number of places per status. There's just one counter for the total number of non-free places in an area. Seats.io does not keep the information of how many places are in a custom status ("myCustomStatus" in the example above), and how many are booked. It just knows the total of places that are either booked or have a custom status.

That means you can't change the status of a specific set of places from a custom status to booked. But the good news is that you don't need to do anything: the counter already indicates the total number of non-free places. So, for example, if you were to first mark 5 places as "reserved", and then book "those" 5 places, a total of 10 places would be non-free (which is not what you want).