Manage a vending machine's planogram (product-to-slot mapping) programmatically via a VMS API.
domain: developerhub.nayax.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Create or select a Product Map in the VMS (e.g., Nayax Core: Administration > Product Maps), scoped to an operator and machine model.
Use the Lynx API's machine products endpoint to add one or multiple products to a specific machine's product map in a single request.
Use the platform's Planogram Wizard (or equivalent visual tool) to confirm the shelf/bin layout matches the intended planogram before publishing.
Set the product map's active/inactive status appropriately so machines only pick up maps intended for production use.
Re-pull the machine's product/planogram state after applying changes to confirm slot-to-SKU and price mappings landed correctly.
Known gotchas
A product map is defined at the operator plus machine-model level, not per individual machine — assigning the wrong model's map to a machine can silently mismatch slot layouts.
Adding products to a map via API does not guarantee visual/slot correctness — the visual Planogram Wizard view is the way to catch bin/shelf mismatches that a flat product list will not surface.
Inactive product maps will not take effect — a planogram update that succeeded via API can still fail to reach the machine if the map's status was not set to active.
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?