Authenticate to the Revel API using the Bearer token OAuth flow from https://authentication.revelup.com/oauth/token
Query completed orders for a specific business date by GETting from the Order or OrderHistory resource on https://[yoursubdomain].revelup.com/resources/ with date range filters applied as query parameters
Retrieve labor data by querying the scheduling and time-tracking resources; use the Scheduling API to pull employee logged time and shift records for the target date range
Transform the retrieved sales and labor records into the schema required by your BI or reporting platform, mapping Revel fields to the destination system's data model
Load the transformed data into the BI platform via its ingestion API or file import mechanism; run reconciliation checks by comparing Revel's reported totals against the ingested aggregates
Schedule the export to run automatically after end-of-day processing; consider submitting DateRange parameters in UTC to avoid timezone-related date boundary errors
Known gotchas
OrderHistory and Order resources may return different subsets of data; use OrderHistory for finalized records and Order for in-progress state
Revel business dates may not align with calendar midnight in the restaurant's local timezone; confirm how Revel defines business day boundaries for the locations you are exporting
The Scheduling API requires explicit permissions; ensure your API credentials include scheduling scope before attempting to pull labor data
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