# Waze Route & ETA Scraper (`romy/waze-route-eta-scraper`) Actor Run live route calculation, walking distance, and batch ETA queries against Waze's real-time routing engine, for an array of route request objects in a single run. No account or API key needed — each request authenticates itself anonymously. Derived from romy/waze-all-in-one-api. - **URL**: https://apify.com/romy/waze-route-eta-scraper.md - **Developed by:** [Romy](https://apify.com/romy) (community) - **Categories:** Travel - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $4.68 / 1,000 route request processeds 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? An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes. 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. Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md. ## 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. Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run. For examples already wired to this Actor's own input schema, see the [API](#api) section below. Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`). # README ### What does Waze Route & ETA Scraper do? **Waze Route & ETA Scraper** takes an array of route request objects and pushes live route calculation, walking distance, or batch ETA results — one dataset row per request. It talks directly to the same internal protocol the official [Waze](https://www.waze.com/) Android app uses (`rt.waze.com`), reverse-engineered by live MITM capture against a real device and cross-referenced against the app's own decompiled protobuf schema (see `proto/waze_rt.proto`, copied verbatim from [Waze All-in-One API](https://apify.com/romy/waze-all-in-one-api), this Actor's parent). No Waze account, no API key — each request mints its own short-lived anonymous session server-side. This is the route/ETA slice of that parent Actor, split out as its own focused, batch-run scraper. ### Why use Waze Route & ETA Scraper? - **Three operations, one input array** — route calculation, walking distance, and batch ETA, mixed freely in a single run - **Live traffic, not a static distance matrix** — the same real-time routing engine behind the app's own navigation - **Batch ETA in one call per request** — `eta-batch` fans one origin out to many destinations server-side, useful for dispatch/delivery routing without one `route` call per stop - **No account needed** — every request authenticates itself anonymously - **Use cases:** logistics/routing risk analysis, delivery dispatch ETA, travel-time estimation for many origin/destination pairs ### How it connects to the parent This Actor is a narrow spin-off of [Waze All-in-One API](https://apify.com/romy/waze-all-in-one-api), which exposes every reverse-engineered Waze endpoint as an always-on Standby REST API. This Actor wraps only the parent's `/route`, `/walking-distance`, and `/eta-batch` endpoints as a normal batch Actor: give it an input array, get a dataset of results back. ### Input | Field | Type | Description | | ---------- | ----- | ------------------------------------------------------------ | | `requests` | array | **Required.** One or more route request objects (see below). | Each item in `requests`: | Field | Type | Applies to | Description | | --------------------- | --------------------- | --------------------------- | ----------------------------------------------------------------------------- | | `operation` | string | all | `"route"`, `"walking-distance"`, or `"eta-batch"` | | `fromLat` / `fromLon` | number | all | Origin coordinates | | `toLat` / `toLon` | number | `route`, `walking-distance` | Destination coordinates | | `destinations` | array of `{lat, lon}` | `eta-batch` | One or more destinations | | `vehicleType` | string | `route`, `eta-batch` | Confirmed live values include `"PRIVATE"` (default), `"MOTORCYCLE"`, `"TAXI"` | | `maxRoutes` | integer | `route` | Number of route alternatives to return, default `3` | Example: ```json { "requests": [ { "operation": "route", "fromLat": -6.1754, "fromLon": 106.827, "toLat": -6.1274, "toLon": 106.6577 }, { "operation": "walking-distance", "fromLat": -6.1754, "fromLon": 106.827, "toLat": -6.178, "toLon": 106.83 }, { "operation": "eta-batch", "fromLat": -6.1754, "fromLon": 106.827, "destinations": [ { "lat": -6.1274, "lon": 106.6577 }, { "lat": -6.1954, "lon": 106.8206 } ] } ] } ``` ### Output One dataset row per request item, `{ request, result }`: ```json { "request": { "operation": "route", "fromLat": -6.1754, "fromLon": 106.827, "toLat": -6.1274, "toLon": 106.6577 }, "result": [ { "totalLength": 31365, "totalSeconds": 1986 }, { "totalLength": 27001, "totalSeconds": 2909 } ] } ``` `walking-distance` result is a single number (`meters`) or `null`. `eta-batch` result is an array of `{ lat, lon, seconds }`, echoing each destination with its live ETA in seconds (`seconds` is `null` if that leg failed). ### Known limitations - **`route` results don't include route line geometry.** Waze encodes it with Google's S2 cell geometry format, which isn't decoded by this Actor — distance, ETA, traffic comment, and warnings are all real-time and accurate, only the polyline itself is omitted. (Inherited from the parent.) - A malformed request item (missing required fields for its `operation`) is skipped with a logged error rather than failing the whole run. - This is an unofficial, reverse-engineered integration, not affiliated with or endorsed by Waze / Google. Behavior may change if Waze changes its protocol. ### Pricing Pay per event: **$0.006** per `route` — charged once for each route/walking-distance/eta-batch request item successfully processed (Free plan price; lower on paid Apify plans). See the Actor's Pricing tab for current tiered rates. # Actor input Schema ## `requests` (type: `array`): Each item needs "operation" ("route" | "walking-distance" | "eta-batch"), "fromLat"/"fromLon", and then either "toLat"/"toLon" (route, walking-distance) or "destinations" (eta-batch, array of {lat, lon}). "vehicleType" (default "PRIVATE") and "maxRoutes" (route only, default 3) are optional. ## Actor input object example ```json { "requests": [ { "operation": "route", "fromLat": -6.1754, "fromLon": 106.827, "toLat": -6.1274, "toLon": 106.6577 }, { "operation": "walking-distance", "fromLat": -6.1754, "fromLon": 106.827, "toLat": -6.178, "toLon": 106.83 }, { "operation": "eta-batch", "fromLat": -6.1754, "fromLon": 106.827, "destinations": [ { "lat": -6.1274, "lon": 106.6577 }, { "lat": -6.1954, "lon": 106.8206 } ] } ] } ``` # Actor output Schema ## `dataset` (type: `string`): No description # 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 = { "requests": [ { "operation": "route", "fromLat": -6.1754, "fromLon": 106.827, "toLat": -6.1274, "toLon": 106.6577 }, { "operation": "walking-distance", "fromLat": -6.1754, "fromLon": 106.827, "toLat": -6.178, "toLon": 106.83 }, { "operation": "eta-batch", "fromLat": -6.1754, "fromLon": 106.827, "destinations": [ { "lat": -6.1274, "lon": 106.6577 }, { "lat": -6.1954, "lon": 106.8206 } ] } ] }; // Run the Actor and wait for it to finish const run = await client.actor("romy/waze-route-eta-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 = { "requests": [ { "operation": "route", "fromLat": -6.1754, "fromLon": 106.827, "toLat": -6.1274, "toLon": 106.6577, }, { "operation": "walking-distance", "fromLat": -6.1754, "fromLon": 106.827, "toLat": -6.178, "toLon": 106.83, }, { "operation": "eta-batch", "fromLat": -6.1754, "fromLon": 106.827, "destinations": [ { "lat": -6.1274, "lon": 106.6577, }, { "lat": -6.1954, "lon": 106.8206, }, ], }, ] } # Run the Actor and wait for it to finish run = client.actor("romy/waze-route-eta-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 '{ "requests": [ { "operation": "route", "fromLat": -6.1754, "fromLon": 106.827, "toLat": -6.1274, "toLon": 106.6577 }, { "operation": "walking-distance", "fromLat": -6.1754, "fromLon": 106.827, "toLat": -6.178, "toLon": 106.83 }, { "operation": "eta-batch", "fromLat": -6.1754, "fromLon": 106.827, "destinations": [ { "lat": -6.1274, "lon": 106.6577 }, { "lat": -6.1954, "lon": 106.8206 } ] } ] }' | apify call romy/waze-route-eta-scraper --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,romy/waze-route-eta-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/g4GPdEBC4tFuhLyQZ/builds/jbvxcW1bBZ6aLubOL/openapi.json