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://tiles.traffic.api.here.com

https://traffic.api.here.com

Tiles

Incidents, Flow, or Flow Availability

Production environment.

 

https://tiles.traffic.cit.api.here.com

https://traffic.cit.api.here.com

Tiles

Incidents, Flow, or Flow Availability

CIT environment

For more information about the available environments, see HERE Server Environments

Path

/traffic/6.0/

For tiles and flowavailability resources

/traffic/6.2/

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

Application Code &app_code={YOUR_APP_CODE} All requests Substitute your own unique app_code.
Application Id &app_id={YOUR_APP_ID} All requests Substitute your own unique app_id.

For further information, see Examples.