Route a SmartMoving inbound lead to a specific branch using the Lead API
domain: help.smartmoving.com · 4 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Look up the target branch's SmartMoving branch ID via your SmartMoving settings
Append &branchId={branchId} to the standard Lead API URL: https://api.smartmoving.com/api/leads/from-provider/v2?providerKey={provider_key}&branchId={branchId}
Submit the same JSON lead payload structure used for the standard Lead API POST
Confirm in SmartMoving that the new lead is associated with the intended branch rather than the default one
Known gotchas
Branch IDs are account-specific values pulled from SmartMoving settings, not arbitrary branch names or codes
Omitting branchId does not cause an error — the lead is simply processed under the account's default routing, which can mask a misconfiguration
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?