Build a Flipdish POS integration that accepts or rejects orders within the auto-reject window
domain: developers.flipdish.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Get API access and read the Flipdish menu-structure and getting-started guides before building
Subscribe to the order.created webhook (or poll GET /orders with state=ReadyToProcess at most every 20-60 seconds if webhooks aren't viable) to detect new orders
Retrieve full order details via the GET Order endpoint, inspecting OrderState, RequestedForTime, IsPreOrder, and Voucher/Customer/Store data
Accept the order via the accept-order endpoint or reject it via the reject-order endpoint before the auto-reject deadline
Handle the store-closed edge case, where the acceptance timer doesn't start until the store's next opening time
Known gotchas
Orders must be accepted within 13 minutes of OrderCreatedTime or Flipdish auto-rejects them on your behalf — a slow POS integration silently loses orders
Metadata stored on menu items/options is not encrypted at rest and is visible to anyone with menu access — never store sensitive data there
If a store is closed when the order comes in, the countdown pauses until opening rather than starting immediately — don't hardcode a fixed 13-minute SLA from webhook receipt time
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?