Carrier FMCSA Violations

Carrier FMCSA Violations Endpoint

Retrieve standalone FMCSA violation history (per-inspection violation rows) for one or more carriers, without pulling FMCSA detail, sightings, equipment, scores, or insurance.

Need everything at once (FMCSA detail, equipment pairings, sightings, and all FI-aligned sections)? Use GET /carrier/profile instead ( Carrier Profile Endpoint ) — it returns everything in one call. basic_scores.*.violation_summary there gives aggregated counts; this endpoint gives per-inspection detail.

Authentication

• Include your Access-Token in the header of your requests.

• Include your x-api-key The API key provided by GenLogs. This header must be included in the request.

Permissions

Permission	Effect
external-api-carrier-fmcsa-violations	Required to access this endpoint

Endpoint

• URL: https://api.genlogs.io/carrier/profile/fmcsa/violations

• Method: GET

Headers

• Access-Token: (string, required): Access token obtained from the "Create Access Token" endpoint.

• x-api-key (string, required): The API key provided by GenLogs.

Query Parameters:

• usdot_number (array of string, required): One or more USDOT numbers; repeat the parameter for multiple values, e.g. ?usdot_number=10553&usdot_number=2350084.

• start_date (string, optional): Inclusive start date (YYYY-MM-DD) for inspection_date filtering. Omit for full history.

• end_date (string, optional): Inclusive end date (YYYY-MM-DD) for inspection_date filtering. Omit for full history.

Understanding FMCSA violations information

Responses are grouped by USDOT. Each USDOT that exists in FMCSA data returns a violations array (empty if no violations in range); USDOTs that don't exist are omitted from the response entirely. Violations are sorted by inspection_date descending (most recent first).

FMCSA Violations returns one object per USDOT:

• violations (array): One entry per inspection violation record.

  • report_number: (string, nullable) The inspection report number.

  • inspection_date: (string, nullable) Date of the inspection (YYYY-MM-DD).

  • violation_code: (string, nullable) FMCSA violation code.

  • description: (string, nullable) Human-readable violation description.

  • vins: (array of string, nullable) VIN(s) associated with the violation.

  • basic_category: (string, nullable) BASIC category the violation rolls up to (e.g. Unsafe Driving).

  • basic_severity_weight: (integer, nullable) FMCSA severity weight for the violation.

  • oos: (boolean, nullable) Whether the violation resulted in an out-of-service order.

  • oos_weight: (integer, nullable) Out-of-service weight, if applicable.

Response:

• 200 OK: A JSON object containing a violations array per requested USDOT.

• 400 Bad Request: If usdot_number is missing/empty, exceeds the allowed limit, or start_date/end_date is not valid YYYY-MM-DD.

• 401 Unauthorized: If the authentication credentials (Access-Token) is missing or incorrect.

• 403 Forbidden: If the external-api-carrier-fmcsa-violations permission has not been added to your user.

• 404 Not Found: If none of the requested USDOT numbers exist.

• 500 Internal Server Error: If there is an issue on the server that prevents processing the request.

Response Body:

• Data (object): Set of { "violations": [...] } objects grouped by usdot_number.

Request Example:

curl --location 'https://api.genlogs.io/carrier/profile/fmcsa/violations?usdot_number=10553&start_date=2025-01-01&end_date=2025-09-01' \
--header 'Access-Token: {your-user-token}' \
--header 'x-api-key: {your-x-api-key}'

Response Example:

{
  "10553": {
    "violations": [
      {
        "report_number": "CA123456",
        "inspection_date": "2025-03-14",
        "violation_code": "392.2S",
        "description": "Speeding 6-10 mph over limit",
        "vins": ["1FUJA6CK67LX14816"],
        "basic_category": "Unsafe Driving",
        "basic_severity_weight": 5,
        "oos": false,
        "oos_weight": null
      }
    ]
  }
}

Get carrier FMCSA violations

get

Retrieve standalone FMCSA violation history (per-inspection violation rows) for specified USDOT numbers, without pulling FMCSA detail, sightings, equipment, scores, or insurance. Violations are sorted by inspection_date descending (most recent first). Roles must include external-api-carrier-fmcsa-violations.

Query parameters

usdot_numberstring[]Required

USDOT numbers to get FMCSA violations for

start_datestring · dateOptional

Inclusive start date (YYYY-MM-DD) for inspection_date filtering. Omit for full history.

end_datestring · dateOptional

Inclusive end date (YYYY-MM-DD) for inspection_date filtering. Omit for full history.

Header parameters

Access-TokenstringRequired

Token for authentication

x-api-keystringRequired

GenLogs generated API Key for authentication

Responses

200

Successful response

application/json

400

Bad Request - invalid or missing usdot_number, or invalid start_date/end_date

application/json

401

Unauthorized – missing token

application/json

403

Forbidden – invalid token or insufficient permissions

application/json

404

Not Found - none of the requested USDOT numbers exist

application/json

500

Internal Server Error

application/json

get/carrier/profile/fmcsa/violations

GET /carrier/profile/fmcsa/violations?usdot_number=text HTTP/1.1
Host: api.genlogs.io
Access-Token: text
x-api-key: text
Accept: */*

{
  "10553": {
    "violations": [
      {
        "report_number": "CA123456",
        "inspection_date": "2025-03-14",
        "violation_code": "392.2S",
        "description": "Speeding 6-10 mph over limit",
        "vins": [
          "1FUJA6CK67LX14816"
        ],
        "basic_category": "Unsafe Driving",
        "basic_severity_weight": 5,
        "oos": false,
        "oos_weight": null
      }
    ]
  }
}