ClearSky

JLG Timeseries API:

The JLG Timeseries API provides data for your entire fleet—both Legacy and current ClearSky Smart Fleet-equipped machines—for a convenient, single source of all telematics messages. API requests' start and end timestamps correspond to the message-received time, not the machine event time, eliminating the need for redundant or overlapping call periods. The events are displayed in pages of 500 records per page.

The recommended calling frequency for customer requests is every fifteen minutes for the past fifteen minutes of data, with no timeframes overlapping. API requests should be made regularly, calling for the entire fleet’s data. Calls are limited to a maximum timeframe of 1 hour (3600 seconds). Calls for timeframes larger than this will receive a HTTP Error 400. Requests made by equipmentID are allowed up to ten every five minutes. API requests are recommended to be performed synchronously. Please contact JLG for guidance if asynchronous requests are required due to fleet payload volume. After request limits are exceeded, an HTTP Error 429 will be thrown. Call schemes not conforming to the guidance outlined herein may be suspended.

ISO Current State API:

By default, the ISO Current State API strictly follows the ISO/TS15143-3 standard for a current state API. However, optional parameters can provide more data and an expanded page size. Unlike the JLG Timeseries API, which provides records based on timeseries events, the ISO Current State API retrieves the most recent values reported by the machine.

Machine records are provided in pages of 100 records per page, but can be optionally expanded to 1000. For fleets of over 100 machines, the recommended record size per page is 1000. It is recommended to include electric data in the request to receive all relevant machine data. All available pages should be requested in sequence to ensure data for all machines in your fleet is received.

The recommended calling frequency for customer requests is every fifteen minutes for the past fifteen minutes of data. Data responses are cached, which will result in the same payload response if called more frequently. API requests are recommended to be performed synchronously. Please contact JLG for guidance if asynchronous requests are required due to fleet payload volume. After request limits are exceeded, an HTTP Error 429 will be thrown. Call schemes not conforming to the guidance outlined herein may be suspended.

Download the ClearSky Postman Collection