Handle Clover webhook notifications in a server-side callback: parse objectId from each notification object and complete endpoint verification via the developer dashboard
domain: docs.clover.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Register a publicly reachable HTTPS callback URL in the Developer Dashboard under Your Apps > App name > App Settings > Webhooks.
Click 'Send Verification Code'; Clover POSTs a JSON body containing a verificationCode field to your callback URL.
Copy the verificationCode value from the incoming POST body, paste it into the Verification Code field on the Edit Webhooks page, and click Verify to activate the endpoint.
When live events arrive, parse the nested notification objects under merchants[merchantId]; each object contains objectId (e.g. 'O:GHIVJT2ABCRSC'), type ('CREATE' or 'UPDATE'), and ts (Unix milliseconds).
Use the objectId prefix (e.g. 'O:' for orders, 'P:' for payments) to determine the entity type, then call the Clover REST API with the bare ID to retrieve full entity details.
Known gotchas
The notification field is objectId, not eventId; using the wrong key will silently yield undefined and break downstream lookups.
The verificationCode is delivered to your callback URL via an inbound POST from Clover, not returned by an API call; you must read it from the request body and paste it into the dashboard manually.
A single webhook POST may contain notifications for multiple merchants and multiple events per merchant; iterate all entries rather than reading only the first.
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?