Traffic API Developer's Guide

Traffic Incident Data

The basic incidents data request is described under Quick Start. The following list contains links to examples that illustrate further common use cases for requesting traffic incident data from the Traffic API.

The following general request patterns are supported:

Table 1. Traffic incident request patterns
Addressing scheme URL pattern
[Z]/[X]/[Y] {base-url}/{path}/{resource}/{format}/{zoom}/{column}/{row}?
Quadkey {base-url}/{path}/{resource}.{format}?quadkey={quadkey}
Bounding box {base-url}/{path}/{resource}.{format}?bbox={bounding box coordinates}
Proximity {base-url}/{path}/{resource}.{format}?prox={proximity coordinates}
Corridor coordinates {base-url}/{path}/{resource}.{format}?corridor={corridor coordinates}

You cannot use this account to purchase a commercial plan on Developer Portal, as it is already associated to plans with different payment methods.

To purchase a commercial plan on Developer Portal, please register for or sign in with a different HERE Account.

Something took longer than expected.

The project should be available soon under your projects page.

Sorry, our services are not available in this region.

Something seems to have gone wrong. Please try again later.

We've detected that your account is set to Australian Dollars (AUD).
Unfortunately, we do not offer checkouts in AUD anymore.
You can continue using your current plan as normal, but to subscribe to one of our new plans,
please register for a new HERE account or contact us for billing questions on