Draw an adjacency edge between two tables
/api/link-adjacenciesBoth tables must already belong to the SAME book_table_link_groups row (an ordinary combine group, never a furniture-set piece, which has its own separate combo mechanism); validated server-side, not just by the parser. No Venue Pro gate: an edge only refines an already-created group's own combining behaviour, it cannot create a new combinable group. Idempotent on a duplicate (alreadyExists: true), since the canvas' click-to-connect toggle already checks its own edge list before calling this: a repeat only fires on a genuine race between two staff drawing the same line at once.
Authorization
sessionCookie 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
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 POST "https://example.com/api/link-adjacencies" \ -H "Content-Type: application/json" \ -d '{ "tableAId": "168a9ff3-a8f5-446f-9317-a12a92d4feed", "tableBId": "29442673-3f7b-4c34-b398-f20a1a1539d7" }'{ "ok": true, "edgeId": "313dce2b-2b39-4003-a757-6d5975c65a7b", "alreadyExists": true}List a combine group's staff-drawn adjacency edges GET
Every book_table_link_adjacencies edge for one book_table_link_groups id (2026-09-11): which of the group's own tables actually sit next to each other, drawn on the floor-plan canvas' connect tool. Combining that group's members now requires a connected chain of these edges (see reservation-slots.ts's own comment); an empty list means every member is bookable only on its own or with a single-table fit.
Remove an adjacency edge DELETE
Deletes one book_table_link_adjacencies row. Both tables and their group are untouched: this only withdraws staff's claim that the two tables sit next to each other, the same way removing a furniture-set combo withdraws a combining permission without touching the pieces it named.