API Endpoint: FMCSA Carrier

The fmcsa-carrier endpoint verifies a motor carrier's FMCSA operating status by USDOT number.

POST /api/v1/validate/fmcsa-carrier

https://www.tincomply.com/api/v1/validate/fmcsa-carrier

Looks up a motor carrier by USDOT number and returns whether it is allowed to operate, its operating authority by type (common, contract, broker), insurance filings, out-of-service status and fleet size.

Request body

FieldTypeDescription
dotrequired string The USDOT number. Not an MC docket number.

Response object: fmcsaCarrierResult

FieldTypeDescription
foundboolTrue when the USDOT number exists.
legalName, dbaNamestringRegistered legal and DBA names.
allowedToOperate, statusCodestringFMCSA operating status (Y or N) and status code.
commonAuthorityStatus, contractAuthorityStatus, brokerAuthorityStatusstringOperating authority by type: A active, I inactive, N none.
bipdInsuranceOnFile, bipdInsuranceRequired, bipdRequiredAmountstringLiability (BIPD) insurance filing and requirement, in thousands of dollars.
cargoInsuranceOnFile, bondInsuranceOnFilestringCargo insurance and broker bond filings.
oosDatedatetimeOut-of-service order date. Present only when the carrier is under an out-of-service order.
totalPowerUnits, totalDriversintFleet size.
safetyRating, carrierOperation, phyStatestringSafety rating, operation type and physical state.
retrievalDatedatetimeWhen we retrieved the record.
messagestringHuman-readable summary of the result.
completedboolFalse when the upstream source was unavailable. The request is retried automatically; call request-details with the request id later to get the finished result.

The sample shows a carrier that is not allowed to operate. A missing insurance filing is not proof a carrier is uninsured, only that no filing is on record with FMCSA.

What to do with this result

When you seeDo this
allowedToOperate is NDo not tender loads to this carrier.
oosDate is presentThe carrier is under an out-of-service order. Do not dispatch.
The authority you need is not AThe carrier is not authorized to act in that role (common, contract or broker).
bipdInsuranceOnFile is below bipdRequiredAmountRequest a current certificate of insurance before booking.
found is falseCheck that you sent the USDOT number, not the MC docket number.
completed is falseThe source was unavailable. Keep the request id and call request-details later; the result fills in once the retry succeeds.

Sample request

curl -X POST https://www.tincomply.com/api/v1/validate/fmcsa-carrier \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"dot":"2213141"}'

Sample response

{
  "id": "qphvFoRev0qje4MyNGc3ywc8",
  "request": {
    "dot": "2213141",
    "requestDate": "2026-10-06T03:03:14Z",
    "requestedServices": "fmcsa-carrier"
  },
  "fmcsaCarrierResult": {
    "dot": "2213141",
    "message": "Not allowed to operate",
    "found": true,
    "completed": true,
    "legalName": "TEST HAULAGE LLC",
    "allowedToOperate": "N",
    "statusCode": "I",
    "commonAuthorityStatus": "I",
    "contractAuthorityStatus": "N",
    "brokerAuthorityStatus": "N",
    "bipdInsuranceRequired": "Y",
    "bipdRequiredAmount": "750",
    "totalPowerUnits": 4,
    "totalDrivers": 4,
    "carrierOperation": "Interstate",
    "phyState": "OH",
    "retrievalDate": "2026-10-06T03:03:14Z"
  }
}

Errors

Requests that cannot be processed return HTTP 400 with an object keyed by field name, each listing what was wrong. Authentication, permission and other status codes are covered in Errors & service status.

This endpoint requires an API key with the Validate permission.

See how this check works in the portal and what it costs: FMCSA Carrier Verification