Frequently Asked Questions




      What browsers do you support?
      Both the chart renderer and chart designer work well in Chrome, Firefox, Safari, Opera, IE Edge, IE11 and IE10.
      Our chart renderer also works in IE9.
      Can I integrate with PayPal/Stripe/Payment Provider X? 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.
      Can I use in Wordpress/Magento/Joomla?

      The short answer is: yes, of course! is technology-agnostic. That means you can integrate it into any modern web platform, including Wordpress, Magento and Joomla.

      However, you need to do some programming to make work with your event management plugin. We don't offer a solution that works out-of-the-box.

      A basic integration comes down to:

      • Writing JavaScript code to show the chart to ticket buyers
      • Calling our API from your server to actually book a seat, after the ticket buyer has selected his seats.

      Please refer to our getting started guide on how to do this.

      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 seating chart.
      For more information, please refer to the documentation for Android's WebView and iOS's WKWebView components.
      Can I temporarily reserve seats?
      Yes, you can. See this recipe for more information.
      How do I suggest best available seats to 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.
      Can I print my floor plans?
      Yes of course!
      To do so, you'll need to render your floor plan using print mode (i.e. using 'mode: "print"'), and then use the print functionality of your browser. Print mode will disable zooming and panning, and make sure no object is selectable.
      Can I prevent people from leaving empty spaces, aka orphan seats, when selecting their seats?
      By simple configuration of your floor plan: use a noOrphanSeats selection validator and implement the onSelectionInvalid callback to actually prevent proceeding to checkout.
      Which peak load can your servers handle?

      As far as peak load is concerned, there are 2 things to consider:

      • the maximum number of chart renderings per minute
      • the maximum number of bookings per minute

      To render charts, we rely heavily on edge caching (by Amazon CloudFront). All JS, HTML and CSS is served by a CDN. We only hit our own servers to fetch the chart and the seat statuses for the event - which are cached in memory. 60k renderings per minute is a load we can handle comfortably.

      When booking we hit our database (Postgres) to persist the data. CDNs or in-memory caching don't help much in that respect. Still, we can handle about 30k bookings per minute with our current setup - and we can easily scale up the infrastructure with the push of a button if needed.

      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 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.
      How do I sell season tickets?
      Easy: specify an array of events instead of a single event in the renderer and in the API.
      Do you support multiple languages?
      Yes! We currently support over 30 languages out-of-the-box, and we regularly add new ones.
      For more details, please see this page.


      What is an "event"?
      If you sell the seats in a venue one time, that’s what we call an event. So an event is a single performance of a show, a single football match, a single concert.
      A 'group of events' is what we call a season, even if it contains just 3 single events on consecutive days, or even on the same day.
      What is a "booked seat"?
      A booked seat is a seat that is firmly assigned to a customer at the end of the booking process. In technical terms, it is defined as

      the first statusChange of a seat (or GA available space) in an event. All subsequent statusChanges for that seat for that event are included in the same single count. Sole exception is temporary reservation of a seat by use of “reserveOnSelect”, which does not trigger count if it is the only statusChange used.
      This means that the whole process of one end customer actually using one seat (normally resulting in a booking for a specific event), regardless of the number of status changes necessary to achieve that, is counted as one use.
      This also means that a booked seat is not necessarily the same as a sold ticket. For example: when an end customer books a seat, but the ticket is free or paid for by a sponsor, we still consider that to be a booked seat.

      Note: 'booked seat' replaces 'used seat', which is the term we previously used. They mean the exact same thing, for all intents and purposes.
      When I book a whole table, does that count as a single booked seat?
      We count usage based on the number of seats on a table. If a booked table contains 8 seats, we charge for those 8 seats.
      What does "whitelabeling" mean?
      It means your customers won't see the powered by link on the bottom right of floor plans that are rendered within your web application. As a result, the floor plans look like a fully integrated part of your own website.
      Can I use only parts of (like the floor plan designer)?
      No. We believe in simplicity and efficiency. Splitting up parts of the plugin would make things much more complicated, both from a business and technical point of view, which would, in the end, force us to push up pricing. That’s why we only offer the full package.
      Can I install on my own servers?
      No. is a Software as a Service (SaaS) application that runs in the cloud. We maintain our servers, security and updates so that you don't have to. Again, this allows us to offer the pricing we do.
      What is the difference between your monthly and yearly plans?
      Monthly plans are always postpaid: we invoice you at the end of each month.
      Yearly plans are prepaid: you pay up front for an entire year for the number of booked seats mentioned. In return you get the flexibility to spread usage over a full year instead of month to month, particularly useful if you have high seasonal variation.
      If your usage goes above the number purchased during the prepaid year, we invoice the over-usage monthly in arrears, based on actuals.
      How can I pay?
      We'll send you a monthly or yearly invoice, which you can pay by PayPal or wire transfer.
      What does "90 days free use for integration & demo purposes" mean?
      Using on your site requires some integration work. We don’t charge for access to and use of during this integration and testing period, and we will answer support questions through email or the chatbox on our website.
      However, there is a time limit of 90 days, and you can’t use it in full production mode to actually sell seats. In order to switch on production mode, you need to contact us at and sign up to your selected payment plan.
      Do you offer high-volume discounts?
      Yes we do. Please contact us at and let us know what volume you anticipate and can commit to.
      Do you offer discounts to non-profit users or customers?
      No, we don’t. In short, we believe the value of our offering is the same, and we offer a pricing that is based on the value we provide.
      Furthermore, we’re not convinced that non-profits only “do good”, where for-profits only “do business”. Jason Fried (Basecamp founder) wrote an excellent blog post on the topic.
      Do you offer a Service Level Agreement (SLA)?
      Yes, we do on Enterprise plans, i.e. for volumes over 240K seats / year or 20K seats / month. Our SLA is available here.