Authenticate to the Revel API by obtaining a Bearer token from https://authentication.revelup.com/oauth/token and confirm that your application has the required permissions to manage establishment resources
Query existing tables and floor plan sections by issuing GET requests to the relevant resources on https://[yoursubdomain].revelup.com/resources/; identify the resource name for tables and dining sections in the Revel API reference
Create a new table by POSTing to the table resource endpoint with required fields such as name, section or floor identifier, seating capacity, and any position data used for floor plan rendering
Update table properties (for example, renaming, changing capacity, or reassigning to a different section) using PUT or PATCH requests to the specific table resource URL with the table ID
Associate orders with tables by including the table identifier when creating or updating an order through the Order resource, enabling floor-plan-based order management
Verify changes by GETting the table resource and confirming the fields match the intended configuration before pushing the setup to a live service period
Known gotchas
Table resource availability and field names in Revel's API should be verified against the current API reference; the Revel API has approximately 140 public resources and naming conventions should be confirmed in the developer portal documentation
Floor plan position data (x/y coordinates or layout identifiers) may only render correctly within the Revel POS app interface; API-managed position values may not translate to the visual layout without POS-side configuration
The Revel API uses both legacy subdomain-based base URLs and the newer api.revelsystems.com platform; confirm which base URL supports table management resources for your account
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp