Fleet Telematics Custom Routes Developer's Guide

Constructing a Request

A typical request to the Fleet Telematics Custom Routes 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://s.fleet.ls.hereapi.com

https://fleet.ls.hereapi.com

Production environment when you use an API Key or an authentication token. For more information, see the Identity & Access Management Developer Guide.

Legacy Base URL

https://pde.api.here.com

https://maps.gfe.api.here.com

Production environment when you use an app_id/app_code pair. For the available authentication options, see the Identity & Access Management Developer Guide.
Path /1/  
Resource

doc/attributes

doc/layer

doc/layers

doc/maps

file

index

indexes

search/bbox

search/corridor

search/proximity

search/quadkey

serviceconfiguration

static

tile

tiles

 
Application Code - Legacy &app_code={YOUR_APP_CODE} Substitute your own unique app_code. For more information, see the Identity & Access Management Developer Guide.
Application Id - Legacy &app_id={YOUR_APP_ID} Substitute your own unique app_id. For more information, see the Identity & Access Management Developer Guide.
API Key &apiKey={YOUR_API_KEY} Substitute your own unique apiKey. For more information, see the Identity & Access Management Developer Guide.
This example request uses HTTP GET to view map data from a specific layer:
https://s.fleet.ls.hereapi.com/1/tile.json
?apiKey={YOUR_API_KEY}
&layer=LINK_ATTRIBUTE_FC1
&level=9
&tilex=537
&tiley=399
Note: This example uses a HERE API Key to authenticate your request. For the available authentication options, see the Identity & Access Management Developer Guide.