Get ProDemand labor times and specs through an API

What you can build on ProDemand

• Get labor times for a job

  Build this

  Selects the vehicle, opens the labor operation in the Estimate Guide and reads its labor time, additional and combination times, notes and OEM parts.

  Takes

  Year, make, model, engine, labor operation

  Returns

  Operation, labor hours, additional time, combination time, inclusions and notes, OEM part numbers, MSRP

• Get the maintenance services due

  Build this

  Selects the vehicle with its odometer reading, opens the Maintenance module and reads the indicator, mileage and timed services that apply.

  Takes

  Year, make, model, engine, odometer reading

  Returns

  Service type, service, interval, fluid type, fluid capacity, notes

• Look up a trouble code in 1Search Plus

  Build this

  Selects the vehicle and searches a DTC in 1Search Plus, reading the search results, the related components and the cards returned for the code.

  Takes

  Year, make, model, engine, trouble code

  Returns

  Code description, related components, related procedures, card titles

• Get a specification with QuickSpecs

  Build this

  Searches a specification for the selected vehicle and reads the Common Specs card: the specification searched and its associated table.

  Takes

  Year, make, model, engine, specification

  Returns

  Specification, value, unit, associated table rows

Automate ProDemand with a workflow

A workflow runs your methods as one process, with nobody at the screen. A schedule or a call from your own system starts it, the steps run in order, and the result arrives in your inbox or in the systems you already use.

• Labor and parts for each new repair order

  Build this

  Starts

  When your shop system calls the workflow's webhook with a vehicle and a job

  Step 1

  Get labor times for the job from the Estimate Guide for that vehicle.

  Step 2

  Keep the labor hours, additional and combination times and the OEM parts with MSRP.

  Step 3

  Post the result to your shop management system's webhook, under the repair order number.

• Maintenance due for today's appointments

  Build this

  Starts

  Every weekday at 7:00

  Step 1

  For each vehicle on today's appointment list, get the maintenance services due at its odometer reading.

  Step 2

  Group the services by vehicle with a short summary of what to offer.

  Step 3

  Email you the list before the first appointment.

• Trouble code briefing for the technician

  Build this

  Starts

  When your shop system calls the workflow's webhook with a vehicle and a DTC

  Step 1

  Look up the trouble code in 1Search Plus for that vehicle.

  Step 2

  Summarize the code description, related components and procedures in a few lines.

  Step 3

  Post the briefing to your team's Slack webhook with the repair order number.

You can run a workflow by hand on every plan, Free included. Schedules and webhook triggers come with the paid plans, from $29 a month.

Once built, one call from your code

Once you have built a method, it is one POST to /v1/runs from your backend, or a tool an AI agent calls over MCP. This is what “Get labor times for a job” would look like.

curl https://api.fous.com/v1/runs \
  -H "Authorization: Bearer $FOUS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "method": "prodemand.com/get_labor_times",
    "input": {
      "year": 2019,
      "make": "Ford",
      "model": "F-150",
      "engine": "3.5L V6 Turbo",
      "operation": "Water pump, replace"
    }
  }'

{
  "status": "completed",
  "data": {
    "vehicle": "2019 Ford F-150 3.5L V6 Turbo",
    "operation": "Water pump, replace",
    "labor_hours": 4.8,
    "additional_time": [
      {
        "description": "With tow package",
        "hours": 0.3
      }
    ],
    "combination_time": [
      {
        "description": "Thermostat, replace",
        "hours": 0.4
      }
    ],
    "notes": "Includes drain and refill cooling system.",
    "parts": [
      {
        "description": "Water pump assembly",
        "oem_part_number": "WP-48213",
        "msrp": 312.45,
        "quantity": 1
      }
    ]
  }
}

An example with invented data, not a ready-made endpoint. The method exists in your organization once you build it, and its name, inputs and fields follow your request.

ProDemand’s own options

ProDemand has no API for repair shops. Mitchell 1 reviews API requests from commercial software providers, enterprise customers and integration partners, and does not approve requests from individual repair facilities. Shops use ProDemand in the browser, or pick labor and parts in the Estimator from inside approved partner software.

Read on November 12, 2026: Mitchell 1 API request, ProDemand Estimate Guide, ProDemand user documents.

Signing in to ProDemand

You open ProDemand from the Login link at prodemand.com, in Chrome, Firefox or Edge, with the account on your shop's ProDemand subscription. With Fous you sign in once through ProDemand's own sign-in with your own account. The login is sealed with AES-256, never returned by the API or written to logs, and code and AI agents never see it.

Worth knowing

Every lookup starts with a vehicle

You select the vehicle first, and ProDemand then opens 1Search Plus. The odometer reading is entered at vehicle selection, so a maintenance method takes it as an input with year, make, model and engine.

Labor time is more than one number

Additional time and combination time are listed right after the main labor operation, with inclusions and notes. Mitchell 1's own estimating guide says to add them, so a method returns them as separate fields.

Part prices are MSRP

The Estimate Guide shows OEM part numbers with MSRP. Mitchell 1 notes that parts prices vary by area, so treat them as list prices and check with your supplier for exact prices.

Cards appear only when there is data

1Search Plus returns a card only when there is relevant information behind it, ordered by the usual diagnosis and repair sequence. A method's list of cards can differ from one vehicle and code to the next.

More in Automotive: aftermarket and fleet

• Autossimo
• AutoZonePro
• Burson EzyParts
• First Call Online
• NAPA PROLink
• Nexpart
• Omnipart
• Repco Navigator Pro
• Qapter
• Mitchell Cloud Estimating
• PartsTrader
• Auto Integrate
• 1link Service Network
• Decisiv SRM
• WORLDPAC speedDIAL
• CollisionLink
• RepairLink
• partslink24
• PartsTech
• SilverDAT
• ALLDATA Repair
• ARMS Automotive Suite

Other industries: Cars.com Dealer Center, Gusto, Payapps, 1688, 楽天市場 RMS, National Student Clearinghouse secure site.