Fleet Telematics Route Matching Developer's Guide

Constructing a Request

A typical request to the Fleet Telematics Route Matching 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://m.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://rme.api.here.com Production environment when you use an app_id/app_code pair. For more information, see Authentication Examples.
Path /2/  
Resource matchroute  
Application Id - Legacy &app_id={YOUR_APP_ID} Substitute your own unique app_id . For more information, see Authentication Examples.
Application Code - Legacy &app_code={YOUR_APP_CODE} Substitute your own unique app_code. For more information, see Authentication Examples.
API Key &apiKey={YOUR_API_KEY} Substitute your own unique apiKey . For more information, see Authentication Examples.
This example search request uses HTTP GET to get the most probable route for a small GPS trace (zipped and Base64-encoded CSV file):
https://m.fleet.ls.hereapi.com/2/matchroute.json
?apiKey={YOUR_API_KEY}
&routemode=car
&file=UEsDBBQAAAAIANmztEQSwaeZzwAAAM8BAAAQAAAAc2FtcGxlLXRyYWNlLmdweIXPTQuCM
BwG8HufQnZv%2F605S0k9djEIungdZjpSJ27kPn6%2BRBgYXcYYv2cPzzG2deU8805L1YSIYoLiaHMs
Wvv9uBlYowOrZYhKY9oAoO973DOsugJ2hFBIz8k1K%2FNabGWjjWiy%2FJ36ShjVqqITd2lxpmo4XVK
gMP6vZaCneKIyYabivzHnr4BhCbb6hoZRpnvMp86L%2BdIapxImRJxiSuh%2Bj5xq7CWY%2Bcz1Eayp
A10qxlfVjvOl8rxVxfzDQrk%2FFCfLRs7YpOCzA%2BZd49LoBVBLAQIUABQAAAAIANmztEQSwaeZzwA
AAM8BAAAQAAAAAAAAAAEAIAAAAAAAAABzYW1wbGUtdHJhY2UuZ3B4UEsFBgAAAAABAAEAPgAAAP0AAA
AAAA%3D%3D
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 Route Matching, see Authentication Examples