Table combinations
list_table_combinations read
Section titled “list_table_combinations ”List the table combinations set up for the restaurant (which tables can be joined and the party sizes they cover). Use before adding or removing one.
Required scope: floor-plan.read
| Parameter | Type | Required | Description |
|---|---|---|---|
brand |
string | no | Brand slug. Optional in JWT mode. |
add_table_combination write
Section titled “add_table_combination ”Let two or more tables be joined for a large party. Use when an owner says ‘tables 5 and 6 can combine to seat up to 8’. Give the table names (or ids) plus the min/max party the joined set seats. The tables must be on the same floor plan and in the same dining area (assign them to an area first if they aren’t).
Required scope: floor-plan.write
| Parameter | Type | Required | Description |
|---|---|---|---|
brand |
string | no | Brand slug. Optional in JWT mode. |
tables |
array | yes | Two or more table names or ids that can be joined, e.g. [“5”,“6”]. |
minParty |
number | yes | Smallest party the joined tables should seat. |
maxParty |
number | yes | Largest party the joined tables can seat. |
idempotencyKey |
string | no |
remove_table_combination write
Section titled “remove_table_combination ”Remove a table combination by its id (from list_table_combinations). Use when tables should no longer be joined.
Required scope: floor-plan.write
| Parameter | Type | Required | Description |
|---|---|---|---|
brand |
string | no | Brand slug. Optional in JWT mode. |
combinationId |
string | yes | Combination id (from list_table_combinations). |
idempotencyKey |
string | no |