Skip to main content

inspections

Inspections Data​

When requesting a full Carrier profile, the recent_inspections field will contain up to 50 of the most-recent inspections from the past two years.

Inspections Object​

This is the data that is always present with a Carrier Profile returned by our API. This type of data is updated on a monthly basis.

fieldtypedescription
inspection_idstringUnique identifier for the inspection
report_idstringUnique identifier for the inspection
inspection_datedateDate the inspection occurred
report_statestringThe state/region/province where the inspection occurred
out_of_service_totalnumberThe number of out of service violations associated with this inspection
is_post_accidentbooleanIf true, indicates the inspection occurred post-accident
has_doa_arrestbooleanIf true, indicates the inspection resulted in at least one drug or alcohol arrest
violationsarrayList of violations associated with this inspection
hazmat_oos_totalnumberThe number of hazmat OOS violations from this inspection

Example Inspections Data​

Here is an example of what type of information that might be contained in an inspection object: 

{
    "inspection_id": 123456789,
    "report_id": "NE00012345",
    "inspection_date": "2023-01-01T00:00:00.000Z",
    "report_state": "NM",
    "out_of_service_total": 0,
    "has_doa_arrest": false,
    "is_post_accident": false,
    "violations":[...],
    "hazmat_oos_total": 0
}

Violations Data​

Inspections can contain 0 or more violations in the violations field.

Violations Object​

This is an object that contains data about a violation that was logged during an inspection. The type of each violation can be found in the federal code using the part & sequence numbers. Similar types of violations can be grouped into categories and referenced using their category id ( https://ask.fmcsa.dot.gov/euf/assets/mcmiscatalog/d_inspection6.html ). These categories can be further grouped into three kinds of violations: "Driver Violations", "Hazmat Violations", or "Vehicle Violations"

The table below describes the fields within a violation object:


Example Violation Data​

Here is an example of what type of information that might be contained in a violation object: 

{
  "inspection_violation_id": 987654321, 
  "sequence_number": 2,
  "part_number": 393,
  "part_number_section": "45B2",
  "inspection_violaton_unit": "2",
  "inspection_violation_category_id": 16,
  "out_of_service": true,
  "defect_verification_id": 1
}
Finding Violation Details

To find more information about what was in violation, refer to the part_number and part_number_section fields. In this example, the part number and section refer to 393.45(b)(2).

According to https://www.ecfr.gov/current/title-49/subtitle-B/chapter-III/subchapter-B/part-393/subpart-C/section-393.45 - this specific violation is refering to "Brake tubing and hose must be secured against chaffing, kinking, or other mechanical damage"

fieldtypedescription
inspection_violation_idstringUnique identifier for this violation
sequence_numbernumberSequence number of the violation
part_numbernumberRefers to the part of the federal code this violations falls under.
part_number_sectionnumberRefers to the specific section (within the part) of the federal code that this violations falls under.
inspection_violation_unitstringThe unit/vehicle this violation applies to
inspection_violation_category_idnumberSimilar violations in the federal code are grouped into categories. These categories can be found at https://ask.fmcsa.dot.gov/euf/assets/mcmiscatalog/d_inspection6.html
out_of_servicebooleanWhen true, this is an out-of-service violation. These types of violations are more critical than non-OOS violations.
defect_verification_idnumberIdentifies what happened as a result of the inspection.

1=Repaired At Scene
2=Towed/Escorted to repair service
3=Non-OOS/Driver Non-OOS
4=Other
99=Unknown/Unverified