Submit a new inbound lead to SmartMoving via the Lead API
domain: help.smartmoving.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Retrieve your Provider Key from SmartMoving Settings > Sales > Lead Providers > Your Website > View Instructions
Build a JSON payload with either FirstName+LastName or a single FullName (not both), plus optional PhoneNumber, Email, MoveDate, MoveSize, and Notes fields
Provide Origin/Destination as either the individual street/city/state/zip components or a single AddressFull field, not a mix of both
POST the payload with header Content-type: application/json to https://api.smartmoving.com/api/leads/from-provider/v2?providerKey={provider_key}
Handle the HTTP 400 duplicate-submission error by informing the user rather than silently retrying
Also email a copy of every form submission to yourself as a fallback in case the API POST fails
Known gotchas
SmartMoving rejects duplicate submissions with an HTTP 400 and a specific error message; your form must catch this rather than treat it as a generic failure
Fields not in the documented list are not rejected — they are silently appended to the lead's Notes section instead of being stored as structured data
MoveSize values that don't match an existing value in your SmartMoving Move Size settings will auto-create a new Move Size entry rather than erroring
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?