Waze API — Real-Time Traffic, Alerts & Road Incidents
Pricing
from $5.60 / 1,000 alerts & jams queries
Pull real-time Waze traffic data via API: accidents, hazards, police reports, road closures and live jams in any map area, plus driving directions with on-route alerts and venue search. Clean geo-coded JSON rows for logistics, routing, fleet and mobility analytics. No Waze account needed.
🎯 PICK ONE OPERATION PER RUN. Each run produces one clean dataset matching the chosen mode.
recordType.💡 TIP: Alerts & Jams is the core real-time-traffic operation. Use Driving Directions for route-level incident enrichment.
↙️ Required for Alerts & Jams and Venues.
Bottom-left corner of the map area (bounding box) as a latitude,longitude pair.
40.66615,-74.13732 — lower-left of a New York City box💡 TIP: Keep the box small (a few km across) for dense, fast results. Pair with the top-right corner to define the rectangle.
⚠️ Ignored for Driving Directions.
↗️ Required for Alerts & Jams and Venues.
Top-right corner of the map area (bounding box) as a latitude,longitude pair.
40.77278,-73.76818 — upper-right of a New York City box⚠️ Ignored for Driving Directions.
For Alerts & Jams — maximum number of alerts to fetch (accidents, hazards, police, road closures). Set to 0 to fetch jams only. Default 20.
For Alerts & Jams — maximum number of traffic jams to fetch. Set to 0 to fetch alerts only. Default 20.
Optional. For Alerts & Jams — only return alerts of specific types, as a comma-separated list. Values: ACCIDENT, HAZARD, JAM, ROAD_CLOSED, POLICE, CONSTRUCTION, MISC.
POLICE,HAZARDLeave blank for all types.
Optional. For Alerts & Jams — only return alerts of specific subtypes, as a comma-separated list (e.g. POLICE_HIDING, ROAD_CLOSED_EVENT, HAZARD_ON_ROAD_CONSTRUCTION). Leave blank for all subtypes.
Optional. For Venues — only return venues in specific categories, as a comma-separated list (e.g. RESTAURANT,PARKING_LOT,ICE_CREAM). Leave blank for all categories.
Optional. For Venues — Waze zoom level 1–4 (4 is most zoomed in). Default 1. Higher zoom returns more granular venues.
🟢 Required for Driving Directions.
Starting point as a latitude,longitude pair.
32.0853,34.781767⚠️ Ignored for other operations.
🔴 Required for Driving Directions.
Destination as a latitude,longitude pair.
32.794046,34.989571⚠️ Ignored for other operations.
Optional. For Driving Directions — when enabled, each route row includes the full route polyline (routeCoordinates). Off by default to keep rows compact.