AEMP API
The Bobcat Telematics API allows you to access machine data for your fleet. The API is implemented following the AEMP Telematics standard 15143-3 provided by the Association of Equipment Management Professionals.
Once authenticated, response to every request will be sent in XML format. The responses conform to the XML Schema documents provided by the International Organization for Standardization.
Authentication
All API requests are secured using the OAuth 2.0 Client Credentials Grant. To generate a token, create a POST request to the Token endpoint.
This endpoint will reach out to the authorization server and return an access token which is used to access data from the Bobcat Telematics API. This access token is used to authenticate the remaining endpoints. It is referred to as 'authorizationToken' in the examples.
Example Request (Content-Type: "application/x-www-form-urlencoded"):
{
"scope": "api:aemp national",
"grant_type": "client_credentials",
"client_id": "<YOUR_CLIENT_ID>",
"client_secret": "<YOUR_CLIENT_SECRET>"
}
Example response:
{
"token_type": "Bearer",
"expires_in": 3600,
"access_token": "<YOUR_TOKEN>",
"scope": "api:aemp national"
}
Subscriptions
Some APIs require active Machine IQ Subscriptions to access some or all endpoints. See documentation on each API for more information.
| Data Point | Basics / Standard | Health & Security / Premium |
|---|---|---|
| Location | X | X |
| Cumulative Operating Hours | X | X |
| Fuel Remaining | X | X |
| DEF Remaining | X | X |
| Engine Status | X | X |
| Diagnostic Codes | X | |
| Fuel Used | X | |
| Cumulative Idle Hours | X |
Paging
Any endpoints that return more than one piece of equipment or list of telematics data is paged. This navigation is controlled by the page number parameter present on the endpoint URL. By default, a maximum of 100 records is returned by page.
Caching
Same API requests will be cached for an interval of 1 hour.