Check FMCDealer recalls from your own systems

What you can build on FMCDealer

• Check a VIN for open field service actions

  Build this

  Reads the OASIS VIN report for one VIN and returns the vehicle and every open field service action listed on it.

  Takes

  VIN

  Returns

  VIN, vehicle, FSA number, FSA title, FSA type

• Get the FSA VIN List for a recall

  Build this

  Reads the FSA VIN List for one FSA number on the FSA VIN Lists site and returns the dealership's VINs, with owner names and addresses once released.

  Takes

  FSA number

  Returns

  FSA number, VIN, vehicle, owner name, owner address

• Open an SSSC approval request for a VIN

  Build this

  Submits an Approval Request contact on the SSSC Web Contact Site for one VIN and FSA, with the P&A code and photos of the VIN, repair order and part.

  Takes

  VIN, FSA number, repair order number, P&A code, photos of the VIN, repair order and part

  Returns

  Contact status, approval code when given

Automate FMCDealer 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.

• Open FSAs on used vehicle inventory

  Build this

  Starts

  When your DMS calls the workflow's webhook with the VINs in used stock

  Step 1

  For each VIN sent, read the OASIS VIN report and its open field service actions.

  Step 2

  Keep the VINs with an open FSA that was not there on the last run.

  Step 3

  Email you the list with VIN, vehicle, FSA number and FSA title.

• Open FSAs on tomorrow's service appointments

  Build this

  Starts

  When your scheduling system calls the workflow's webhook with tomorrow's VINs

  Step 1

  For each appointment VIN, read the open field service actions in OASIS.

  Step 2

  Keep the VINs with at least one open FSA.

  Step 3

  Post VIN, FSA number, FSA title and FSA type to your service system's webhook.

• New VINs and owner details on your FSA VIN Lists

  Build this

  Starts

  Every Monday at 7:00

  Step 1

  For each FSA number you name, get the FSA VIN List.

  Step 2

  Keep the VINs that are new or have owner details changed since the last run.

  Step 3

  Post FSA number, VIN, vehicle, owner name and owner address to your recall follow-up system's webhook.

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 “Check a VIN for open field service actions” would look like.

curl https://api.fous.com/v1/runs \
  -H "Authorization: Bearer $FOUS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "method": "fmcdealer.dealerconnection.com/check_vin_open_fsas",
    "input": {
      "vin": "1FTFW1E50PKA00001"
    }
  }'

{
  "status": "completed",
  "data": {
    "vin": "1FTFW1E50PKA00001",
    "vehicle": "2023 F-150 XLT SuperCrew 4x4",
    "open_field_service_actions": [
      {
        "fsa_number": "26S21",
        "title": "Rear axle bolt inspection",
        "type": "Safety Recall"
      },
      {
        "fsa_number": "25C07",
        "title": "Body control module software update",
        "type": "Customer Satisfaction Program"
      }
    ]
  }
}

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.

FMCDealer’s own options

Ford's dealer bulletins send dealers to OASIS and the FSA VIN Lists site to find affected vehicles, and to the SSSC Web Contact Site for approvals, each used on screen. Claims are entered from the dealer management system (DMS) or in One Warranty Solution (OWS) online. The bulletins describe no API for dealership staff.

Read on November 12, 2026: Ford dealer bulletin, Safety Recall 26S13 (via NHTSA), Ford dealer bulletin, Safety Recall 25S01 Supplement #1 (via NHTSA).

Signing in to FMCDealer

FMCDealer sends you to Ford's Microsoft sign-in page, where you sign in with your dealer account and password and an MFA code. With Fous, you sign in once through that same page with your own account, and the login is sealed with AES-256 and never shown to your code or AI agents.

Worth knowing

Owner names arrive after the VINs

For Safety Recall 26S13, FSA VIN Lists opened on March 5, 2026 and owner names and addresses followed on March 27, 2026. Read the list again after the release to get the owner details.

Owner data is for recall follow-up only

Ford's bulletins say owner names and addresses on FSA VIN Lists come from registration records, and using them for anything other than the recall breaks the law in several states.

Some recalls need SSSC approval first

For Safety Recall 25S01, the SSSC had to approve the repair from photos of the VIN, the repair order and the part, and its approval code was required on the claim.

Claims are rejected without STST certification

In the U.S., FSA claims on repair orders opened from August 31, 2024 are not paid unless the repairing technician holds STST Competency 10 certification.

More in Automotive: dealers

• GM GlobalConnect
• Honda Interactive Network
• Kia KDealer+
• NNAnet
• Stellantis DealerCONNECT
• Toyota Dealer Daily
• Dealertrack uniFI
• RouteOne
• VinSolutions Connect CRM
• Dealertrack DMS
• ACV Auctions
• OPENLANE
• Ally Dash
• Copart
• IAA
• USS CIS
• vAuto Provision
• AutoScout24 Händlerbereich
• CarGurus Dealer Dashboard
• mobile.de Händlerbereich
• Cars.com Dealer Center
• Auto Trader Portal
• AUTO1.com
• Manheim

Other industries: The Work Number, BuildingConnected, Tradeplace, 千牛卖家中心, Slate, British Gas Business online account.