Video Application Messages

When the iOn Vision service is activated, LMUs begin sending application messages to CTC that provide information about the events that triggered a video upload for the EDVR (enhanced DVR) videos. The LMU sends these application messages using a service profile that is separate from the LMU’s inbound server setting. After the service profile is activated and devices are sending video events to CTC, there are two ways to retrieve information about the video events.

The iOn Vision Video API has endpoints to return events by ESN or account. This is a stripped version of the application message with the created time, links to the videos for download, and a few other fields. You can download the video events as follows:

  • By ESN: GET {{BaseURL}}/videos/events/devices/esn/{{ESN}}
  • From an account: GET {{BaseUrl}}/videos/events/accounts/{{accountId}}

CTC also stores the whole application message, which can be downloaded using CTC’s Result Services or Data Pump. The entire application message has useful information, such as the video quality, type of video (time lapse versus full motion), and tripId. The full application message also includes the LMU location associated with the video and the event code.

To download the latest events with Result Services, use the following endpoint:


For a production deployment, you will likely want to set up Data Pump to poll for the application messages as they come in across your fleet of vehicles. Data Pump setups use a first-in-first-out queue for all devices in an account to allow efficient polling of all CTC messages. This is typically how customer applications ingest data from CTC.

The endpoint used to gather results with Data Pump is

NOTE: The BaseURL for iOn Vision APIs is, whereas Result Services and Data Pump use the BaseURL The URLs are often shortened for brevity in CTC's documentation.