Fleet Telematics Custom Locations Developer's Guide

Constructing a Request

A typical request to the Fleet Telematics Custom Locations 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 https://cle.api.here.com Production environment
Path /2/  
Resource

layers/delete

maps/delete

layers/access/grant

layers/list

layers/modify

layers/upload

search/all

search/bbox

search/corridor

search/proximity

search/quadkey

search/routeisoline

search/tile

calculaterouteisoline

 

Format

Supported formats:
  • .json
  • .txt
 
Application Code &app_code={YOUR_APP_CODE} Substitute your own unique app_code
Application ID &app_id={YOUR_APP_ID} Substitute your own unique app_id

This example search request uses HTTP GET to request locations within 5 kilometers of a point in Berlin, Germany in layer MY_STORES:

https://cle.api.here.com/2/search/proximity.json
?app_id={YOUR_APP_ID}
&app_code={YOUR_APP_CODE}
&proximity=52.50795,13.54728,5000
&layer_ids=MY_STORES

If the layers doesn't exist, you can create it: http://fleet.cit.api.here.com/2/layers/upload.json?app_id={YOUR_APP_ID}&app_code={YOUR_APP_CODE}&layer_id=MY_STORES&file=NAME%09CITY%09WKT%0d%0aBurger%20Place%09Frankfurt%09POLYGON%20((13.54728 52.50785, 13.54708 52.50795, 13.54728 52.50815, 13.54748 52.50795, 13.54728 52.50785))