Pricing
$1.25 per 1 000

Flow and incidents on the same graph your routes use.

A jam factor that maps to a link the router already knows means you can explain an ETA instead of just serving one. Incidents come with geometry, criticality and a validity window.

Free
2.5K
HERE list
$2.50
ApiNavi
$1.25
Endpoints
2

Refreshed every 60 seconds

Probe data and sensor feeds merged into link-level speeds, with a confidence value so you can tell a well-observed motorway from a quiet side street.

Referenced, not approximated

OpenLR and shape-based referencing so a jam can be joined to your own network model without a spatial guess.

Incidents with a lifecycle

Start time, expected end, criticality and type. Closures carry the geometry of what is closed, not just a point.

Try it now

Endpoints

The sandbox answers without a key. Response shapes are the documented ones.

curl -sG "https://api.apinavi.com/v1/traffic/flow" \
  -H "Authorization: Bearer $APINAVI_KEY" \
  -d "in=bbox:13.30,52.48,13.48,52.56" \
  -d "locationReferencing=olr,shape"
ResponseSandbox data

Parameters

EndpointParametersRequest
/v1/traffic/flowGETinbbox:13.30,52.48,13.48,52.56
locationReferencingolr,shape
/v1/traffic/incidentsGETincircle:48.86,2.35;r=5000
criticalitymajor,critical
What this costs

All ten billed services

Free allowance first, then the ladder. HERE's published rate is shown struck through.

ServiceFree / monthHERE listApiNavi
TrafficLive flow and incidents on the road graph.2.5K$2.50$1.25
RoutingDoor-to-door routes for car, truck, bike and foot.5K$1.50$0.75

Limits that matter

  • Bounding box up to 100 km per side per request
  • Corridor queries up to 500 km
  • History: 13 months of typical-speed profiles

Coming from HERE? The parameter map is one page away. Read the HERE migration guide

Questions

Is coverage the same everywhere?

No, and that is worth saying plainly. Motorway and arterial coverage is broad across Europe and North America; residential coverage thins out outside metro areas. The coverage page lists it per country.

Can I get traffic inside a routing response instead?

Yes, and that costs nothing extra — routing with a departureTime already accounts for live and historical traffic.