Debug a rejected Supermove inbound lead or update payload
domain: help.supermove.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
In Supermove, go to Settings > View/Edit Company Settings > Lead Providers
Select the specific configured Lead Provider the payload was sent through
Open the Logs tab and click the relevant Request ID
Compare the Request Body (what was sent) against the Response Data (the error returned)
Cross-reference common validation error types — unmatched move size, tags, or project/job variables not configured on the account
Known gotchas
Validation errors usually mean a payload value doesn't match something already configured in the destination Supermove account (move size, tag, or variable), not a malformed JSON structure
Sending a project-level variable that actually belongs on the job (or vice versa) produces a validation error rather than being silently ignored
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?