Get a safety event by id.
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
The token returned when a user authenticated their account. This authorizes access to a specific account.
^con_tkn_\S+$"con_tkn_22vUhkC6tgre4kwaYfUkCDA1rzn6eyb4"
The id of the safety event.
^sft_evt_[0-9A-HJKMNP-TV-Z]{26}$"sft_evt_01D8ZQFGHVJ858NBF2Q7DV9MNC"
Expand resources in the returned response
driver, vehicle, driver,vehicle, vehicle,driver Include raw responses used to normalize model. Used for debugging or accessing unique properties that are not unified.
OK
^sft_evt_[0-9A-HJKMNP-TV-Z]{26}$"sft_evt_01D8ZQFGHVJ858NBF2Q7DV9MNC"
The ID used to represent the entity in the source system.
"123456789"
Every provider has a unique code to identify it across Terminal's system. You can find each provider's code under provider details.
"geotab"
harsh_brake, harsh_acceleration, harsh_turn, speeding, crash, near_crash, tailgating, cell_phone, distracted, drowsiness, smoking, seat_belt_violation, stop_sign_violation, red_light_violation, unsafe_lane_change, camera_obstruction, eating_and_drinking, rolling_stop, unsafe_parking The ID of the vehicle that was involved in the event.
^vcl_[0-9A-HJKMNP-TV-Z]{26}$"vcl_01D8ZQFGHVJ858NBF2Q7DV9MNC"
Internal metadata about the record.
The original event type as defined by the telematics provider's system
"HARD_CORE_BRAKING_MESSAGE"
Entities in Terminal are expandable. Using the expand query parameter you can choose to ingest just an ID or the full entity details.
^drv_[0-9A-HJKMNP-TV-Z]{26}$"drv_01D8ZQFGHVJ858NBF2Q7DV9MNC"
Includes data enriched via third-party vendors. See Extensions
[]