subscribe to clover order webhooks and reconcile order details via follow-up api calls
domain: docs.clover.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
In the Clover Developer Dashboard, go to App Settings > Webhooks and enter a callback URL
Complete the verification handshake: Clover sends a verificationCode to your callback URL, which you copy back into the dashboard to activate the webhook
Select which event categories to subscribe to (e.g., order created/updated) during the Edit Webhooks event subscription step
On receiving a webhook payload containing only an order ID, call the Clover REST API to fetch the full order details
Ensure your app has been granted the read permission corresponding to each subscribed event category, or the merchant-level events won't fire
Known gotchas
Clover webhook payloads include only IDs (e.g., order ID), not full order objects — a separate API call is required to retrieve line items, pricing, and status
Each event category requires its own read permission scope; missing scopes silently prevent those events from being delivered
The verification handshake must be completed per environment (sandbox vs production each need their own verified callback URL)
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?