Overview:

This guide provides detailed information on the expected JSON format for leads coming from Moving.com and how the payloads are processed. It is intended as a technical reference for how a Moivng.com Integration is working. 

Relevant Links: 

• Known Lead Provider Integrations - Link 
• Debugging Inbound Leads - Link
• Moving.com Website - Link 

Integration Settings: 

Inbound Moving.com Payload: 

Note: Inbound payload must be configured to send the data as JSON. 

{
  "project": {
    "customer": {
      "first_name": "NameFirst",
      "last_name": "NameLast",
      "phone_number": "4152222222",
      "email": "test.email@gmail.com"
    },
    "jobs": [
      {
        "move_size": "1 bedroom",
        "date": "2025-05-17",
        "additional_notes": "",
        "locations": [
          {
            "city": "Walnut Creek",
            "state": "CA",
            "zip_code": "94598",
            "address": "Walnut Creek, CA 94598"
          },
          {
            "city": "Carmel",
            "state": "CA",
            "zip_code": "93923",
            "address": "Carmel, CA 93923"
          }
        ], 
        "referral_source":"Moving.com"
      }
    ]
  }
}

Moving.com to Supermove, Payload Specifics: 

• move_size - Moving.com has customizable move_sizes for each customer similar to Supermove. You must ensure that your move sizes match between the two platforms. Un-configured move sizes as part of a lead from Moving.com will be rejected by Supermove.