Fleet Telematics Geofencing Developer's Guide

Constructing a Request

A typical request to the Fleet Telematics Geofencing includes the basic elements shown in the following table and, in addition, it may contain resource-specific parameters or data.

Table 1. Basic request elements
Element Value/Example Description
Base URL - Legacy https://gfe.api.here.com

Production environment when you use an app_id/app_code pair. For more information, see Authentication Examples.
Base URL https://fleet.ls.hereapi.com

Production environment
Path /2/  
Use the CLE resources to manage geofence layers

Query which geofence geometries of a certain layer cover or are close to the given asset position.

GET only, specify request details via query parameters

One of the resource names supported by the service, see Supported Resources

Supported formats:
  • .json
API Key &apiKey={YOUR_API_KEY} Substitute your own unique apikey. For more information, see Authentication Examples.
Application Code &app_code={YOUR_APP_CODE} Substitute your own unique app_code. For more information, see Authentication Examples.
Application Id &app_id={YOUR_APP_ID} Substitute your own unique app_id. For more information, see Authentication Examples.

This example request uses HTTP GET to check if an asset is inside or outside of a particular geofence polygon.

Note: This example uses a HERE API Key to authenticate your request. For information on other possible options, see Authentication Guide. For examples of how to use the other authentication options with the Fleet Telematics Geofencing, see Authentication Examples.
Note: The above example assumes you have uploaded the following WKT file to the service.
1     Kansas   KS     POLYGON((-102.0 40.0,-102.0 37.0,-94.619 37.0,-94.619 39.1074,-95.310 40.0))