Core concepts

Everything you need to know to about the Tables API.

The Tables API is now archived. For up-to-date Pay at Table integrations, please use the Dojo API and EPOS Data API:

Dojo API
EPOS Data API (REST)
EPOS Data API (WebSocket)

tip

In a restaurant setting, a 'table' is often shorthand for a group of diners, seated and currently eating. In the Dojo Tables API, this is called a session. A table refers to a physical table. Payments are associated with the session - specifically with the sessionId. Multiple sessions can be associated concurrently with a single table, to cover business setups like shared tables, counter dining and split bills per table.

Bill Learn more about how bill items work

Payment Learn how to handle payments on your POS

Requestor Learn about each consumer of your EPOS integration

Session Learn about sessions and their life-cycle

Session locks Learn how to safeguard against accounting errors

Table Learn more about the Table object