Push a menu update from Deliverect to a connected delivery channel on demand
domain: developers.deliverect.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate to the Deliverect API using your client credentials to obtain an access token.
Retrieve the list of active channels and location account IDs linked to the restaurant via the accounts endpoint.
Trigger a menu publish by calling the menu publication endpoint with the target channel and location identifiers.
Poll or listen for the publication status callback; Deliverect reports success or failure per channel.
Handle partial-failure responses where some channels accept the menu and others reject items due to validation errors.
Log the menu version and publication timestamp for audit and rollback purposes.
Known gotchas
Not all channels support real-time menu pushes; some platforms impose their own processing delay of minutes to hours after Deliverect submits the update.
Item validation rules differ per destination channel — a modifier option that is valid on one platform may be rejected on another; normalize and validate before publishing.
Deliverect rate-limits menu publication calls per location; batch location updates rather than firing one request per store in a tight loop.
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?