Track your webDEALER title applications through an API

What you can build on webDEALER

• Get returned title applications

  Build this

  Reads the Returned Titles list and, for each application, the reason the county gave in its Transaction History.

  Takes

  County (optional), returned since (optional)

  Returns

  VIN, deal number, county, year and make, owner, returned date, reason for return

• Get DMV Rejected transactions

  Build this

  Searches Title Search for status APPROVE with DMV Rejected Only checked, and reads the Rejection Date and Reason from each Transaction History.

  Takes

  Nothing

  Returns

  VIN, deal number, county, rejection date, reason for the rejection

• Get title groups with payments due

  Build this

  Reads the Reviewed Title Groups with Payments Due page under Payments, Titles Grouped for Payment, with each group's fees.

  Takes

  Nothing

  Returns

  Group ID, county, Total Fees, Pay to County

• Request a retraction

  Build this

  Opens a submitted title application from Title Search, selects Retract and sends the county your reason for the retraction request.

  Takes

  VIN, reason

  Returns

  VIN, application status, retraction requested

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

• Returned title applications, emailed each morning

  Build this

  Starts

  Every weekday at 7:00 Central time

  Step 1

  Get the returned title applications from the Returned Titles list.

  Step 2

  Keep the applications that were not on the list at the last run.

  Step 3

  Email you each VIN, deal number, county and reason for return.

• DMV Rejected transactions, posted to your DMS

  Build this

  Starts

  Every weekday at 8:00 Central time

  Step 1

  Get the DMV Rejected transactions with their rejection date and reason.

  Step 2

  Keep the transactions that were not on the list at the last run.

  Step 3

  Post each VIN, deal number, county and reason for the rejection to your webhook.

• Title groups with payments due, for accounting

  Build this

  Starts

  Every weekday at 9:00 Central time

  Step 1

  Get the title groups from the Reviewed Title Groups with Payments Due page.

  Step 2

  Stop when there are no groups.

  Step 3

  Email you each Group ID, county, Total Fees and Pay to County amount.

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 returned title applications” would look like.

curl https://api.fous.com/v1/runs \
  -H "Authorization: Bearer $FOUS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "method": "webdealer.txdmv.gov/get_returned_title_applications",
    "input": {
      "county": "Travis",
      "returned_since": "2026-11-09"
    }
  }'

{
  "status": "completed",
  "data": {
    "applications": [
      {
        "vin": "3ACME00000N100482",
        "deal_number": "D-20418",
        "county": "Travis",
        "year_make": "2024 Northwind",
        "owner": "Acme Logistics LLC",
        "returned_date": "2026-11-10",
        "reason": "Scanned evidence of ownership is not the original. Upload a scan of the original MCO."
      }
    ],
    "count": 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.

WebDEALER’s own options

TxDMV offers a webDEALER title integration service that dealer management system vendors connect to, and a CSV Title Data Import. Both bring deal data into webDEALER to start title applications. Following them through review, returns and payment is done on the site itself.

Read on November 12, 2026: webDEALER Dealer User Guide (July 2026), webDEALER | ePLATE resources, webDEALER 101.

Signing in to webDEALER

webDEALER signs dealers in with the same username and password as ePLATE, on the Dealers tab of its login page. A session ends after 10 minutes of inactivity, and you must sign in again after one hour of continuous use. With Fous you sign in once through webDEALER's own sign-in with your own account: the login is sealed with AES-256, and an expired session is signed back in.

Worth knowing

Open 6:00 AM to 11:59 PM Central

webDEALER is only available from 6:00 AM to 11:59 PM CST. Schedule workflows inside that window.

Each county authorizes you separately

To submit title applications to several counties, each county tax office must authorize your dealership. Each county also decides whether you or it groups Reviewed titles for payment.

Payment happens outside webDEALER

You pay the county outside webDEALER, ideally by ACH. The payments page shows Total Fees and Pay to County: a Dealer Deputy's Total Fees can include a Title Convenience Fee of up to $10.00.

30 calendar days from sale

With a General Issue Plate, the title transaction must be submitted in webDEALER within 30 calendar days of sale, or 45 if the seller financed.

More in Government: US courts, records, permits and licensing

• Sunshine 811
• Texas811 Portal
• USA North 811
• Accela Citizen Access
• DOB NOW
• Metrc
• The Compliance Engine
• eFileIL
• eFileTexas
• Florida Courts E-Filing Portal
• Odyssey File & Serve
• LOOP

Other industries: Simplifile, Wide Area Workflow, Cal eProcure, INTIME, SIDES E-Response, Fastenal.