Schedule a Virtual Estimate

Prerequisites

• A job must already exist. You'll need its jobId and its current zone.id.
• Authentication headers and zone context (see API Overview).
• Optionally, an existing location ID to attach as the job's origin. If you don't have one, you can create a new location inline.

Step 2 — Ensure the Job Has the Correct Zone

The job's zone determines which estimator pool is available. If the job was created via the intake form or with an explicit zoneId, it already has a zone — skip to Step 3.

If the job doesn't have a zone, or you need to reassign it, use updateJobs with setZone:

mutation SetJobZone($updateJobs: [UpdateJobInput]) {
  updateJobs(updateJobs: $updateJobs) {
    isSuccess
    jobs { id zone { id name } }
  }
}

// Variables:
{
  "updateJobs": [{
    "jobId": "7af1bc10-e356-11ef-8bf8-7dd6e69e92c7",
    "setZone": "zone-uuid-here"
  }]
}

Finding the right zone ID

If you know the zip/postal code but not the zone ID, you can resolve it from the location you just added. Query the job's locations and read the serviceArea field:

query GetJobZone($jobId: String) {
  jobs(filter: { jobIds: ["7af1bc10-..."] }, resolve: ["locations"]) {
    jobs {
      zone { id name }
      locations {
        locationType
        location {
          areaCode
          serviceArea { id name }
        }
      }
    }
  }
}

The serviceArea.id is the zone that the location geographically belongs to. Use that as the setZone value, or pass it directly as zoneInput in the find query below.

Step 4 — Book the Virtual Estimate

The lockWindow mutation is the booking call. It validates that the slot is still available, creates or updates the event, assigns it to the job's zone, and triggers the Yembo integration if enabled.

mutation BookVirtualEstimate(
  $start: Int!
  $end: Int
  $type: String!
  $title: String
  $jobId: String!
  $assetIds: [String]
  $locations: [CalendarEventLocationInput]
  $eventId: String
  $updateEventSequentialOrder: Boolean
  $restrictionsEnabled: Boolean
) {
  lockWindow(
    start: $start
    end: $end
    type: $type
    title: $title
    jobId: $jobId
    assetIds: $assetIds
    locations: $locations
    eventId: $eventId
    updateEventSequentialOrder: $updateEventSequentialOrder
    restrictionsEnabled: $restrictionsEnabled
  ) {
    id
    status
    start
    end
    type
    metadata
    assets { id name metadata }
  }
}

// Variables:
{
  "start": 1737500000,
  "end": 1737501800,
  "type": "virtualEstimate",
  "title": "Virtual Estimate",
  "jobId": "7af1bc10-e356-11ef-8bf8-7dd6e69e92c7",
  "assetIds": ["estimator-asset-id-from-find"],
  "locations": [
    {
      "locationId": "start-location-id",
      "type": "start",
      "order": 1,
      "estimatedTimeAtLocation": 1800
    }
  ],
  "updateEventSequentialOrder": true,
  "restrictionsEnabled": true
}

What lockWindow does server-side

1. 1.Validates the job exists and loads its zone.
2. 2.Re-checks the selected start/end against current availability (unless overrideAvailabilities is true).
3. 3.If eventId is provided, edits the existing event to status: "booked". Otherwise creates a new event.
4. 4.Assigns the event to the job's zone and updates its sequential order on the job timeline.
5. 5.If type === "virtualEstimate" and Yembo is enabled, creates the Yembo Smart Consult room and stores Yembo metadata on the event (see below).

Optional: Create a placeholder first

If you want to create a placeholder event before booking (e.g. to show a "Virtual Estimate needed" item on the job timeline before a slot is chosen), use createCalendarEvent:

mutation CreatePlaceholder {
  createCalendarEvent(calendarEvents: [{
    title: "Virtual Estimate",
    type: "virtualEstimate",
    status: "required",
    jobId: "7af1bc10-...",
    colour: "orange-yellow",
    textColour: "black",
    revenueGenerating: false
  }]) {
    events { id status }
  }
}

Then pass the returned id as eventId in the lockWindow call to convert the placeholder to a booked event.

Full Example — End to End

Here's the complete flow in a single script, from a job with no location to a booked virtual estimate with Yembo integration.

# 1. Set the job's start location (with inline location creation)
curl -X POST "https://moveright.app/api/graphql?zone=ZONE_ID" \
  -H "Content-Type: application/json" \
  -H "Authorization: RefreshToken YOUR_TOKEN" \
  -d '{
    "query": "mutation($u:[UpdateJobInput]){updateJobs(updateJobs:$u){isSuccess jobs{id locations{locationType location{id areaCode serviceArea{id}}}}}}",
    "variables": {
      "u": [{
        "jobId": "7af1bc10-...",
        "addLocations": [{
          "newLocationInput": {
            "addressLineOne": "123 Main Street",
            "areaCode": "90210",
            "city": "Beverly Hills",
            "country": "US"
          },
          "locationType": "start"
        }]
      }]
    }
  }'

# 2. (Optional) Set the zone if the job doesn't have one yet
#    Skip if the job was created with a zoneId or via intake
curl -X POST "https://moveright.app/api/graphql" \
  -H "Content-Type: application/json" \
  -H "Authorization: RefreshToken YOUR_TOKEN" \
  -d '{
    "query": "mutation($u:[UpdateJobInput]){updateJobs(updateJobs:$u){isSuccess jobs{zone{id name}}}}",
    "variables": {
      "u": [{
        "jobId": "7af1bc10-...",
        "setZone": "resolved-zone-id"
      }]
    }
  }'

# 3. Retrieve estimator availability for the next 5 days
curl -X POST "https://moveright.app/api/graphql?zone=ZONE_ID" \
  -H "Content-Type: application/json" \
  -H "Authorization: RefreshToken YOUR_TOKEN" \
  -d '{
    "query": "query($tw:WindowInput!,$af:AssetsFilter,$zi:String){find(timeWindow:$tw,assetsFilter:$af,minNumAssets:1,zoneInput:$zi){windows{start end startTimes assets{id name metadata}}}}",
    "variables": {
      "tw": { "startDate": "2026-07-20", "endDate": "2026-07-25", "minWindowLength": 1800 },
      "af": { "types": ["Estimator"] },
      "zi": "zone-id"
    }
  }'

# 4. Book the virtual estimate with the chosen slot and estimator
curl -X POST "https://moveright.app/api/graphql?zone=ZONE_ID" \
  -H "Content-Type: application/json" \
  -H "Authorization: RefreshToken YOUR_TOKEN" \
  -d '{
    "query": "mutation($s:Int!,$e:Int,$t:String!,$j:String!,$a:[String],$l:[CalendarEventLocationInput]){lockWindow(start:$s,end:$e,type:$t,title:$t,jobId:$j,assetIds:$a,locations:$l,updateEventSequentialOrder:true,restrictionsEnabled:true){id status start end metadata assets{id name}}}",
    "variables": {
      "s": 1737500000,
      "e": 1737501800,
      "t": "virtualEstimate",
      "j": "7af1bc10-...",
      "a": ["estimator-asset-id-from-step-3"],
      "l": [{ "locationId": "start-location-id", "type": "start", "order": 1 }]
    }
  }'

# The lockWindow response will include:
# - id: the booked event ID
# - status: "booked"
# - metadata: Yembo links (if Yembo is enabled)
# - assets: the assigned estimator(s)