# Waze Traffic Scraper (`phantom_coder/waze-traffic-scraper`) Actor Extract 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. - **URL**: https://apify.com/phantom\_coder/waze-traffic-scraper.md - **Developed by:** [Phantom Coder](https://apify.com/phantom_coder) (community) - **Categories:** Travel, Developer tools, Automation - **Stats:** 167 total users, 10 monthly users, 0.0% runs succeeded, 8 bookmarks - **User rating**: 5.00 out of 5 stars ## Pricing from $3.00 / 1,000 scraped results This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events. Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have. Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event ## What's an Apify Actor? Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server. Actors are written with capital "A". ## How to integrate an Actor? If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready. The best way to integrate Actors is as follows. - **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use). - **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`. - **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`. - **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`. - **Any other language** — the [REST API](https://docs.apify.com/api/v2.md). For usage examples, see the [API](#api) section below. For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt). # README ## 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. Select a city from the City preset dropdown, or enter a custom latitude and longitude below it.
  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](#scheduling-for-better-coverage) 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 | |---|---|---|---| | `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 (e.g., `40.7128` for New York City). Ignored when a city preset is selected. | | `longitude` | number | `-74.0060` | Center point longitude (e.g., `-74.0060` for New York City). Ignored when a city preset is selected. | | `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 (city preset):** ```json { "city": "paris", "radiusKm": 15, "includeAlerts": true, "includeTrafficJams": true, "anonymizeUsernames": true } ``` **Example input (custom coordinates):** ```json { "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 ```json { "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 ```json { "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 #### 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 1. **~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. 2. **Point-in-time snapshot** - each run captures one moment. Alerts appear and disappear within minutes. 3. **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. ### Pricing Pay per event - you only pay for each successful result scraped. | Plan | Per 1,000 results | |---|---| | Free | $100 | | Starter | $5 | | Scale | $4 | | Business | $3 | Actor start costs $0.05 per 1,000 runs (negligible). **Typical monthly cost (Starter plan):** - One location, once per hour: ~720 results/month - **~$0.36/month** - One location every 10 minutes: ~4,320 results/month - **~$2.16/month** - One location every 5 minutes: ~8,640 results/month - **~$4.32/month** ### Common use cases ### 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. ### Support Questions or issues? Open a ticket in the **Issues** tab on the Actor page. # Actor input Schema ## `city` (type: `string`): Select a major city to auto-fill coordinates. Leave blank (first option) to enter latitude/longitude manually below. ## `latitude` (type: `number`): Center point latitude (e.g., 40.7128 for New York City). Ignored when a city preset is selected above. ## `longitude` (type: `number`): Center point longitude (e.g., -74.0060 for New York City). Ignored when a city preset is selected above. ## `radiusKm` (type: `number`): Search radius in kilometers around the center point (1-100 km) ## `includeAlerts` (type: `boolean`): Collect traffic alerts (accidents, hazards, police, road closures) ## `includeTrafficJams` (type: `boolean`): Collect traffic jam data with speed and severity information ## `anonymizeUsernames` (type: `boolean`): Remove usernames from data to protect user privacy. It's your responsibility to ensure you have legitimate reasons if collecting identifiable user data. ## Actor input object example ```json { "latitude": 40.7128, "longitude": -74.006, "radiusKm": 10, "includeAlerts": true, "includeTrafficJams": true, "anonymizeUsernames": true } ``` # Actor output Schema ## `dataset` (type: `string`): One record per run containing all traffic alerts, jams, irregularities, and users found within the requested radius. # API You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup. ## JavaScript example ```javascript import { ApifyClient } from 'apify-client'; // Initialize the ApifyClient with your Apify API token // Replace the '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = {}; // Run the Actor and wait for it to finish const run = await client.actor("phantom_coder/waze-traffic-scraper").call(input); // Fetch and print Actor results from the run's dataset (if any) console.log('Results from dataset'); console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((item) => { console.dir(item); }); // 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs ``` ## Python example ```python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token # Replace '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = {} # Run the Actor and wait for it to finish run = client.actor("phantom_coder/waze-traffic-scraper").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}") for item in client.dataset(run.default_dataset_id).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{}' | apify call phantom_coder/waze-traffic-scraper --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,phantom_coder/waze-traffic-scraper" } } } ``` The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer ` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations). ## OpenAPI specification Download the OpenAPI definition: https://api.apify.com/v2/actors/4h4JW9DGsfcpVEphJ/builds/N688coxlwrvqTBBGS/openapi.json