Skip to main content
Tire defects represent issues detected during tire inspections that require attention, ranging from low pressure warnings to critical wear conditions. The defect system categorizes, prioritizes, and tracks issues throughout their lifecycle to help fleet managers maintain safe and efficient operations.

Overview

The Smart Tire API provides access to tire defect history through the Tire Defect Events endpoint. Per request, You can retrieve defects for specific vehicles, groups, or your entire fleet within a date range of up to 6 months.

Defect Structure

Each defect includes comprehensive information to help you understand and address the issue:

Defect Categories

Defects are classified into the following high-level categories:

Defect Types

More specific defect classifications within each category:

Entity Types

Defects can affect different levels of the vehicle:
Axle-level defects typically indicate configuration issues such as mismatched tire brands, sizes, or significantly different wear levels between tires on the same axle.

Severity Levels

Defects are assigned severity levels to help prioritize maintenance:
Critical defects require immediate attention. Vehicles with critical tire defects should be taken out of service until the issue is resolved to prevent safety incidents.

Defect Properties

The properties object contains additional details specific to each defect type:

Common Properties

Filtering Defects

By Severity

Filter to retrieve only defects of specific severity levels:

By Vehicle

Retrieve defects for a specific vehicle:

By Group

Retrieve defects for all vehicles in a group:

Use Cases

Daily Safety Check

Retrieve all critical and major defects from the past 24 hours:

Maintenance Planning

Retrieve all defects to build a maintenance schedule based on severity and due dates:

Alert Integration

Poll for new defects regularly and integrate with your alerting or ticketing system:
  1. Query defects with a recent startDate
  2. Filter for inProgress: true to get active defects
  3. Create tickets or alerts based on severity
  4. Track updateDate to detect status changes
The date range for defect queries cannot exceed 6 months. For longer historical analysis, make multiple requests with consecutive date ranges.