Submit a complex multi-job lead to Supermove via the Developer API New Lead endpoint
domain: help.supermove.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
In Company Settings > Lead Providers, add a Developer API integration and copy its unique endpoint URL
Look up your account's configured Project Type and Job Type identifiers before building the payload
Build a JSON payload with a required project_type, a client object, and a jobs array where each job has a job_type and at least one location object
Only include project/job "values" and "tags" keys that already exist in the account's billing/tag configuration
POST the payload with Content-Type: application/json to the copied endpoint URL
If a payload is rejected, inspect the Lead Provider Logs (Debugging Inbound Leads) for the specific validation error
Known gotchas
Any "values" or "tags" key not already configured in the destination Supermove account causes the entire payload to be rejected, not just that field
This is explicitly the most complex of Supermove's lead integrations — Supermove recommends the Standard Website endpoint unless you need dynamic project/job-type switching
milestones.ad_kind must be exactly "GOOGLE_ADS" or "FACEBOOK", and milestone timestamps must be valid ISO-8601 UTC strings
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?