Waze Traffic Scraper
Under maintenancePricing
from $140.00 / 1,000 scraped results
Waze Traffic Scraper
Under maintenanceExtract real-time traffic data from Waze including accidents, hazards, police reports, road closures, and live traffic congestion. Perfect for logistics routing, fleet optimization, and traffic analysis.
Pricing
from $140.00 / 1,000 scraped results
Rating
5.0
(3)
Developer
Phantom Coder
Maintained by CommunityActor stats
8
Bookmarked
195
Total users
5
Monthly active users
a month ago
Last modified
Categories
Features
Share
Extract real-time traffic data from Waze for any area in the world. Set a center point and a radius, and the Actor returns the current traffic jams and community alerts (accidents, hazards, police, and road closures) from the Waze live map - ready for routing, monitoring, or analysis.
What you get
- Traffic jams - street, city, severity, current speed, length, last update, and the jam's path on the map.
- Community alerts - accidents, hazards, police, and road closures, with type, street, location, and time reported.
- Any area worldwide - from 1 to 100 km radius, or one of 79 city presets.
- Pay only for data - runs that return no data are not charged.
How to use
- Click Try for free on the Actor page.
- Select a city from the City preset dropdown, or enter a custom latitude and longitude below it.
- Set the radius in kilometers (default is 10 km).
- Click Start. Most runs return data in 30 seconds to 5 minutes.
Tip: to monitor an area over time, use Apify's built-in scheduler to run the Actor at a regular interval. Traffic conditions change continuously.
How the data is sourced
The Actor opens the Waze live map in a real browser on a residential proxy from the queried country and collects the traffic data the map loads. Waze protects this data with reCAPTCHA, so not every browser session gets through. The Actor retries with up to seven fresh sessions per run. In the latest October 2026 test, Waze let 11 of 12 runs through across 9 cities.
When a run can't get past the protection, or Waze has no jams or alerts to report in the area, it ends with an empty record and you are not charged. The dataSources field in each record shows what was returned, and dataSources.areaCoverage shows whether the data covers your full radius (full) or the area visible on the map (viewport).
Input configuration
| Field | Type | Default | Description |
|---|---|---|---|
city | string | (none) | City preset - auto-fills coordinates for 79 major cities worldwide. Leave blank to enter latitude/longitude manually. |
latitude | number | 40.7128 | Center point latitude. Ignored when a city preset is selected. |
longitude | number | -74.0060 | Center point longitude. Ignored when a city preset is selected. |
radiusKm | number | 10 | Search radius in kilometers (1-100). |
includeTrafficJams | boolean | true | Collect current traffic jams. |
includeAlerts | boolean | true | Collect community alerts. |
anonymizeUsernames | boolean | true | Remove user identity from any collected alert or user data. |
Example input:
{"city": "paris","radiusKm": 12,"includeTrafficJams": true,"includeAlerts": true}
Output
The Actor saves one dataset record per run, containing all traffic data for the requested area.
Traffic jam
{"id": 1159005400,"street": "A503 - Seven Sisters Rd","city": "Finsbury Park","severity": 4,"lengthMeters": 551,"speedKmh": 4.4,"updatedAt": "2026-10-17T17:42:45.285Z","line": [{ "x": -0.115019, "y": 51.560217 }, { "x": -0.113587, "y": 51.561003 }]}
- severity - Waze jam level from 0 (free flow) to 5 (standstill).
- speedKmh - current average speed along the jam.
- causeAlertId - when present, the
idof the alert that caused the jam. - line - the jam's path as longitude (
x) and latitude (y) points.
Alert
{"id": "alert-182646887/e7e6535e-15ca-4825-b9f2-23edfbf1da03","type": "ROAD_CLOSED","subtype": "","street": "Copse Hill","location": { "x": -0.238146, "y": 51.41832 },"reportedAt": "2026-10-15T18:58:32.000Z","source": "Waze User","reportedBy": "User"}
Common use cases
- Logistics and routing - factor live traffic jams into delivery and fleet routing.
- Traffic analysis - track where and when jams form across an area over time.
- Urban planning and research - study where and when roads slow down.
- Incident awareness - surface accidents, hazards, and road closures as they are reported.
Limitations
- Not every run returns data. Waze protects the live map with reCAPTCHA, and quiet areas may have nothing to report. Runs without data end empty and are not charged. Rerunning usually helps.
- Up to 200 alerts and 200 jams per run. Waze caps each response. For dense cities, use a smaller radius to keep the most relevant results.
- Point-in-time snapshot. Each run reflects conditions at that moment. Schedule regular runs to track changes.
Pricing
Pay per event - you are charged once per run that returns traffic data. Runs that return no data are free.
From October 31, 2026:
| Plan | Per result |
|---|---|
| Free | $0.20 |
| Starter | $0.17 |
| Scale | $0.15 |
| Business and higher | $0.14 |
Until then, the previous prices apply: $0.10 per result on the Free plan and $0.003-0.005 on paid plans.
Actor start costs $0.05 per 1,000 runs (negligible).
Privacy and ethical use
Traffic jam data carries no user identity. Alert and user data is anonymized by default (anonymizeUsernames).
- Only publicly available data is accessed.
- Do not use this data to track or monitor individuals.
- Comply with local privacy laws (GDPR, CCPA, and similar).
Support
Questions or issues? Open a ticket in the Issues tab on the Actor page.