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.
| Element | Value/Example | Description |
|---|---|---|
| Base URL | https://fleet.ls.hereapi.com | Production environment when you use an API Key or an authentication token. For more information, see Authentication Examples. |
| Legacy Base URL | https://cle.api.here.com | Production environment when you use an app_id/app_code pair. For more information, see Authentication Examples. |
| Path | /2/ | |
| Resource | ||
| Format | Supported formats:
| |
| Application Code - Legacy | &app_code={YOUR_APP_CODE} | Substitute your own unique app_code. For more information, see Authentication Examples. |
| Application ID - Legacy | &app_id={YOUR_APP_ID} | Substitute your own unique app_id.For more information, see Authentication Examples. |
| API Key | &apiKey={YOUR_API_KEY} | Substitute your own unique apikey |
This example search request uses HTTP GET to request locations within 5 kilometers of a point in Berlin, Germany in layer MY_STORES:
https://fleet.ls.hereapi.com/2/search/proximity.json
?apiKey={YOUR_API_KEY}
&proximity=52.50795,13.54728,5000
&layer_ids=MY_STORES If the layer does not exist, you can create it:
https://fleet.sit.ls.hereapi.com/2/layers/upload.json
?apiKey={YOUR_API_KEY}
&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))Note: These examples use 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 Custom Locations, see Authentication Examples
