GuidesAPI ReferenceMCPChangelog
Hospitality engine

Rename a link group

patch/api/link-groups/{id}

A group carries nothing but a name, so this is the whole of it. Membership is changed by editing the tables.

Authorization

sessionCookie
sb-qxrvgfkjyvbngipqvslu-auth-token<token>

The dashboard's Supabase Auth session cookie, set at sign-in. Large sessions are split across numbered chunks (…auth-token.0, .1), so treat this as a cookie family rather than one name.

Every request re-validates it against the Auth server (getUser()), never by decoding the cookie locally: a JWT nothing has checked is not a credential. Tenancy is then read from the verified app_metadata.company_id claim and enforced by row-level security; it is never read from request input, on any route, ever.

role (admin / staff) is deliberately not in RLS. It gates specific actions in route code, the operations marked admin below, so hiding a button in the UI is cosmetic only, and a route's own check is the enforcement.

In: cookie

Path Parameters

id*string

Link group id.

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

Response Body

application/json

application/json

application/json

application/json

application/json

curl -X PATCH "https://example.com/api/link-groups/string" \  -H "Content-Type: application/json" \  -d '{    "name": "string"  }'
{  "ok": true}

Create a link group POST

A named run of tables the venue can physically push together to seat a party too big for any single table (migration 0035). Tables join a group through `linkGroupId` on the table itself, so this endpoint only names the group. Two behaviours worth knowing before turning this on. **Grouped tables are allocated LAST**: when a small party fits either a grouped table or an ungrouped one of the same size, the ungrouped one wins, so the run stays whole for a big booking. And **a combination never crosses a group** and never exceeds 4 tables; the cap bounds a subset search reachable from the public availability endpoint.

Delete a link group (admin) DELETE

Never 409s, for the same reason deleting a level does not: `book_tables.link_group_id` is ON DELETE SET NULL (migration 0035), so this un-links its tables and deletes nothing else. Past bookings are unaffected; a reservation holds TABLES (`book_reservation_tables`), never the group they were combined through.