domain: deliverect.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Obtain API credentials and a channelLinkId for the target channel integration from the Deliverect developer portal at developers.deliverect.com
Implement a Menu Update Webhook URL on your system that Deliverect will POST menu data to whenever a customer triggers a menu publish
When a menu publish is initiated, Deliverect delivers a JSON payload to your webhook URL containing the full menu structure keyed by channelLinkId
Parse the incoming menu JSON to build or update your channel's product catalog; map Deliverect item IDs to your internal SKUs
Respond with HTTP 200 to acknowledge receipt; Deliverect treats non-200 responses as failures and may retry
To push product updates from your side, use POST /insert-update-products to upsert items and categories into Deliverect, which then propagates to connected channels
Known gotchas
Deliverect's channel integration model requires you to implement the receiving webhook on your end — you are the channel receiving Deliverect's menu pushes, not the one initiating them via a simple API call
The channelLinkId uniquely identifies a restaurant-channel pairing; a single restaurant with multiple delivery platform accounts will have a distinct channelLinkId per platform
Menu pushes triggered by opening-hours changes use the same webhook payload; handle these idempotently as they may not reflect actual item changes
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?