Generate a merchant access token via Clover's OAuth 2.0 flow from the Developer Dashboard
Fetch current inventory by calling GET /v3/merchants/{mId}/items with expand=itemStock to include stock count data in the response
Use the modifiedTime filter parameter to perform incremental fetches — query only items modified since the last sync timestamp
Update item stock levels by POSTing to /v3/merchants/{mId}/item_stocks/{itemId} with the new quantity value
Register a webhook in the Developer Dashboard pointing to your HTTPS endpoint to receive real-time ITEM and INVENTORY change events
Validate incoming webhooks using the verificationCode sent in the initial POST to your callback URL
Known gotchas
Clover requires a developer app installed on the merchant account to access webhook functionality; the app must be published or in sandbox mode for the merchant to install it
Recently created or updated items may have a brief delay before appearing in bulk GET /items responses due to backend indexing; do not rely on immediate consistency after a write
Access tokens are scoped to the merchant and expire; implement token refresh logic and handle 401 responses by re-initiating the OAuth flow
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