Traffic API Developer's Guide

Constructing a Request

A typical request to the Traffic API includes the basic elements shown in the following table and may contain resource-specific parameters or data

Table 1. Basic request elements
Element Value/Example Purpose Description/comments
Base URL

https://[1..4].traffic.maps.ls.hereapi.com

https://traffic.ls.hereapi.com

Tiles

Incidents, Flow, or Flow Availability

Production environment when you use an API Key or an authentication token. For more information, see Authentication Examples.
Legacy Base URL https://tiles.traffic.api.here.com

https://traffic.api.here.com

Tiles

Incidents, Flow, or Flow Availability

Production environment when you use an app_id/app_code pair. For more information, see Authentication Examples.
Path

/traffic/6.0/

For tiles and flowavailability resources

/traffic/6.3/

For incidents resource

/traffic/6.2/

For flow resource

Resource

tiles

To obtain traffic map tiles

Name of a resource.

Only the GET method is supported. Parameters specify request details. See also Examples.

incidents

To obtain traffic incident data

flow

To obtain traffic flow data

flowavailability

To obtain information on traffic flow availability

Addressing Scheme

Quadkey, [Z]/[X]/[Y], Bounding Box, Corridor or Proximity

Traffic Flow Data

Geographic area for which to retrieve data; options depend on resource/function.

Quadkey, [Z]/[X]/[Y]

Traffic Tiles

Quadkey, [Z]/[X]/[Y], Bounding Box, Corridor or Proximity

Traffic Incidents

Customer Profile or Mapview

Traffic Flow Availability

API Key ?apiKey={YOUR_API_KEY} All requests Substitute your own unique apiKey. For more information, see Authentication Examples.
Application Code - Legacy &app_code={YOUR_APP_CODE} All requests Substitute your own unique app_code. For more information, see Authentication Examples.
Application Id - Legacy &app_id={YOUR_APP_ID} All requests Substitute your own unique app_id. For more information, see Authentication Examples.

For further information, see Examples.