Driver Violations

Driver Violations are recorded instances wherein the Driver has committed Driving, Shift, or Cycle Violations. Whenever a Driver has exceeded the maximum time allowed for an OnDuty or a Driving status within a given time period or a series of time periods, these Driver Violations are recorded.

Fields

Tag Data Type Description
accountId Long The id of the Account that owns this record.
driverHistoryId Long The id for associated Driver History record that triggered this Driver Violation
id Auto-incremented Long Unique Identifier 
lastChangedDate Text Auto-generated timestamp of the last change made to this record
Note: 
Format is in timestamp and timezone (YYYY-MM-DDTHH:MM:SS.sssZ, e.g: 1970-01-01T00:00:00.000Z)
limit Duration The limit at which when the violation would occur.
subsetId Long Indicates the Subset of the Terminal where the Driver is assigned
terminalId Long Id of the Terminal where the Driver is assigned
timestamp Text Time stamp for Driver Violation
Note: Format is in timestamp and timezone (YYYY-MM-DDTHH:MM:SS.sssZ, e.g: 1970-01-01T00:00:00.000Z)
userId Long The id of the Driver who owns the Violation. 
violationName Character (255) Can either be one of the following:

  • CYCLE_DUTY_HOURS
  • SHIFT_DRIVE_HOURS
  • BREAK_DRIVE_HOURS
  • SHIFT_ELAPSED_HOURS

Canada Rules:

  • CAN_DAILY_DRIVE_HOURS
  • CAN_DAILY_DUTY_HOURS
  • CAN_SHIFT_DRIVE_HOURS
  • CAN_SHIFT_DUTY_HOURS
  • CAN_SHIFT_ELAPSED_HOURS
  • CAN_DAILY_OFF_DUTY_HOURS
  • CAN_24MAN_OFF_DUTY_HOURS
  • CAN_CYCLE1_DUTY_HOURS
  • CAN_CYCLE2_DUTY_HOURS
  • CAN_CYCLE2_24OFF_DUTY_HOURS
  • CAN_OIL_WELL_SERVICE

Read

API error calls

ERROR MESSAGE POSSIBLE CAUSES
POST is not supported. POST method is not allowed
PUT is not supported. PUT method is not allowed
DELETE is not supported. DELETE method is not allowed