seats.io

Some pointers to avoid common problems when integrating seats.io into your ticketing system

Integration Checklist

How to define and show seat prices on a rendered floor plan

The new appearance brings a modern look, fluid transitions and clearer visual language to the Renderer and Event Manager.

About multiple price points per seating category, and the difference between ticket types and categories

About multi-language and Internationalisation (i18n) support, supported languages and how to make use of them

Tips on how to decide whether you book your seats via the seats.io API  before or after the payment has been processed

Learn how to pre-assign groups of seats to specific users like sponsor employees, VIPs or guests

This article describes how you can translate the Event Manager, the seats.io tool used by your admin and box office users.

How to override the categories that were assigned through the designer

How to see or edit categories keys, useful when defining pricing.

4 ways to get the selected seat IDs on your server-side code, so you can book them via the Seats API

Temporarily make seats or GA places unavailable for selection, while the ticket buyer finishes up their purchase.

Let people select and book a single seat for multiple events at once

How to make your implementation of objectColor(), objectLabel() and other callbacks blazingly fast

What are regions for, and how can I migrate my account to an other region

Add interactive floor plans to your web application in no time, using these tips

How the seats.io API prevents double bookings + troubleshooting and tips on how to prevent them in your ticketing system

For example, can I use just the floor plan designer, but not the renderer nor the API?

Using seats.io in a CMS (Wordpress, Joomla, Drupal, ...) or eCommerce  platform (Magento, WooCommerce, shopify, ...)