Waze Traffic Scraper

Extract real-time traffic data from Waze — accidents, hazards, police reports, road closures, and live congestion — for any location in the world. Set a center point and a radius, and the Actor returns structured traffic data ready for routing, monitoring, or analysis.

What you get

• Traffic alerts — accidents, hazards, road closures, police traps, and construction zones with location, severity, and community confirmations
• Traffic jams — real-time congestion data including speed, delay, and jam length in metric and imperial units
• Active users — Waze user presence in the area (anonymized by default)
• Configurable radius — search any location worldwide from 1 to 100 km

How to use

1. Click Try for free on the Actor page.
2. Enter the latitude and longitude of your target location.
3. Set the radius in kilometers (default is 10 km).
4. Click Start and wait roughly 30–60 seconds for results.

Tip: To monitor an area continuously, use Apify's built-in scheduler to run the Actor every few minutes. See the Scheduling section below.

---

⚠️ Getting 0 alerts or 0 jams is completely normal. It simply means there is no active traffic data for that location at that moment — the Actor is working correctly.

How to tell if the Actor is working:

• ✅ If you see any users in the results, the Actor is functioning correctly
• ⚠️ If you get 0 alerts, 0 jams, and 0 users, try a busy city center during rush hour — in quiet areas or off-peak hours, all three being zero can still be legitimate

Alerts appear and disappear within minutes. Schedule regular runs to capture traffic as it happens.

---

Input configuration

Field	Type	Default	Description
latitude	number	40.7128	Center point latitude (e.g., 40.7128 for New York City)
longitude	number	-74.0060	Center point longitude (e.g., -74.0060 for New York City)
radiusKm	number	10	Search radius in kilometers (1–100)
includeAlerts	boolean	true	Return traffic alerts (accidents, hazards, police)
includeTrafficJams	boolean	true	Return traffic jam data
anonymizeUsernames	boolean	true	Remove usernames from output to protect user privacy

Example input:

{
  "latitude": 48.8566,
  "longitude": 2.3522,
  "radiusKm": 15,
  "includeAlerts": true,
  "includeTrafficJams": true,
  "anonymizeUsernames": true
}

Output

The Actor saves one dataset record per run containing all traffic data for the requested area.

Alert

{
  "id": "alert-123456",
  "uuid": "abc-def-ghi-jkl",
  "type": "ACCIDENT",
  "subtype": "ACCIDENT_MAJOR",
  "description": "Multi-vehicle accident blocking two lanes",
  "location": { "x": 2.3522, "y": 48.8566 },
  "reportedAt": "2026-04-21T08:30:00.000Z",
  "reliability": 9,
  "confidence": 8,
  "source": "Waze User",
  "reportedBy": "User",
  "thumbsUp": 12,
  "commentCount": 2
}

Traffic jam

{
  "uuid": "jam-xyz-789",
  "street": "Boulevard Périphérique",
  "city": "Paris",
  "country": "FR",
  "level": 4,
  "severity": "Severe",
  "speedKmh": 6.5,
  "speedMph": 4,
  "lengthMeters": 1500,
  "delaySeconds": 540,
  "delayMinutes": 9,
  "reportedAt": "2026-04-21T08:32:00.000Z",
  "route": [
    { "x": 2.350, "y": 48.857 },
    { "x": 2.351, "y": 48.858 }
  ]
}

Understanding the data

Alert types

• ACCIDENT — traffic accidents (MINOR, MAJOR)
• HAZARD — road hazards including ON_ROAD, CONSTRUCTION, and WEATHER subtypes
• POLICE — police presence or speed trap reported by users
• ROAD_CLOSED — road closures
• WEATHERHAZARD — weather-related hazards

Traffic jam severity

Level	Label	Description
1	Light	Minimal slowdown
2	Moderate	Noticeable delay
3	Heavy	Significant slowdown
4	Severe	Very slow movement
5	Standstill	Traffic at a complete stop

Reliability scores

• Reliability (0–10) — overall trustworthiness based on reporter history and confirmations
• Confidence (0–10) — Waze's internal confidence based on number of reports and validations
• Thumbs up — number of users who confirmed the alert is still active

Timestamps

All timestamps are provided in two formats:

• reportedAt — human-readable ISO 8601 format (e.g., 2026-04-21T08:30:00.000Z)
• reportedAtMillis — Unix timestamp in milliseconds for programmatic use

Limitations

• ~200-alert cap — Waze returns a maximum of around 200 alerts per query regardless of area size. In dense cities, use a smaller radius (3–5 km) to focus results.
• Point-in-time snapshot — each run captures one moment. Alerts appear and disappear within minutes.
• Residential proxy required — the Actor uses Apify's residential proxy automatically. A paid Apify plan with the RESIDENTIAL proxy group enabled is required for the Actor to work.

Scheduling for better coverage

Schedule the Actor to run regularly for continuous monitoring. Go to Schedules in Apify Console and use these cron expressions:

Frequency	Cron	Estimated coverage
Every 5 min	*/5 * * * *	50–70% of alerts
Every 10 min	*/10 * * * *	30–50% of alerts
Every 30 min	*/30 * * * *	15–25% of alerts

Multiple locations: for city-wide coverage, run multiple smaller-radius instances rather than one large area.

Common use cases

• Logistics and routing — optimize delivery routes with real-time traffic conditions
• Fleet management — monitor traffic patterns across multiple locations simultaneously
• Urban planning and research — analyze incident frequency and congestion patterns over time
• Alert systems — build notifications for specific incident types in a target area

Privacy and ethical use

User data is anonymized by default. The anonymizeUsernames option (enabled by default) removes all usernames and user IDs from the output.

• Only publicly available data is accessed
• Do not use this data to track or monitor individuals
• Comply with local privacy laws (GDPR, CCPA, etc.)

Support

Questions or issues? Open a ticket in the Issues tab on the Actor page.