Apply for Deliverect integration partner access and complete onboarding to receive your channel credentials and API access to the Deliverect developer environment
Register your POS as a channel in the Deliverect platform by providing your channel identifier, callback endpoint URLs, and supported capabilities
Configure a menu-received webhook endpoint on your side that Deliverect will call when a menu is published to your channel; implement HTTPS with a publicly accessible URL
When the menu webhook fires, parse the Deliverect menu payload containing categories, products, modifiers, and PLU codes, then transform and load the menu into your POS or aggregation layer
Acknowledge the webhook by returning an HTTP 200 response promptly; implement idempotency using the menu version or timestamp in the payload to handle redelivery
Use the Deliverect API to confirm receipt of the menu and mark the channel as active so that orders can begin flowing to your endpoint
Known gotchas
Deliverect menu payloads can be large for enterprise brands with many modifiers; ensure your webhook endpoint can handle large JSON bodies without timeout
Modifier group nesting in the Deliverect schema can be deeper than some POS systems natively support; validate nesting depth against your POS limits before accepting a menu
Failing to acknowledge the menu webhook promptly can cause Deliverect to retry and potentially create duplicate menu-load operations
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