Note: You’ll only find answers to technical and functional questions about seats.io in the list below. For questions about pricing, accounts and the cost of integration, please refer to the FAQ on our pricing page.
Which browsers do you support?
Our chart renderer and chart designer work well in Chrome, Firefox, Safari, Opera, IE Edge, IE11 and IE10. Our chart renderer also works in IE9.
How can I integrate seats.io with PayPal/Stripe/Payment Provider X?
Seats.io is not a standalone application for selling tickets.
Instead, it is a plugin, meant to be integrated into a host system, typically an online ticketing system that also provides payment gateway integration, e-ticket generation, event management tools, and more.
If you’re after a full ticketing system that includes reserved seating capabilities, we suggest taking a look at one of our awesome customers.
Do you offer a native iOS/Android component?
No we don’t, not yet at least.
However, both Android and iOS have a component you can use to display part of web pages as part of your native mobile app. You could use these components to embed a seats.io seating chart.
For more information, please refer to the documentation for Android’s WebView and iOS’s WKWebView components.
How can I design a floor plan for a multi-level venue?
If the venue for which you’re designing a floor plan has multiple levels, with seats located physically above
and below each other, you have two possible solutions: either you draw the venue as if the floors were not on
top of each other, with the seats on the lowest floor closest to the center of the floor plan. Or you can draw
the floors next to each other on the same seats.io chart.
Which of these two is the best option depends on a number of factors, but mainly on the actual number of floors. As a rule of thumb, we recommend to draw floors next to each other if you have more than 2 levels.
Can I temporarily reserve seats?
Yes, you can. See this recipe for more information.
I want to suggest best available seats for my users
For selecting best available seats, you have two options: what we call ‘client side’ and ‘server side’.
Client side means that the ticket buyer sees a seating chart with the suggested best available seats highlighted. He can then choose to go with the suggested seats,
or pick other seats. To have the seating chart select best available seats, pass in the selectBestAvailable parameter to the chart.
On the other hand, server side best available is implemented as a server-side API call. When changing object status, you can request best available seats, instead
of passing in seat IDs. We figure out which seats are the best ones. With server-side best available, ticket buyers don’t see the selected seats in a seating chart.
How do I sell season tickets?
Can I print my floor plan?
Yes of course!
To do so, you’ll need to render your floor plan in an html page, and then use the print functionality of your browser.
Use this code to render the floor plan:
Note the use of
mode: "print". This option will remove the zoom controls and make sure no object is selectable. For more info on the print mode option, check this page.
How can I prevent people from leaving empty spaces when selecting their seats?
In order to warn attendants about orphan seats, you should use the chart config setting
orphanSeats: 'warn' and pass a callback for
onOrphanSeatsChange like so:
Using warn will still allow orphan seats but these will be displayed with an exclamation mark and a tooltip asking the attendee to not leave any empty seats. That said, you should use the
onOrphanSeatsChange to validate the chart and prevent submitting a form with orphan seats.