# Waze Sos Contacts Scraper (`romy/waze-sos-contacts-scraper`) Actor

Get real local emergency and roadside-assistance contacts from Waze. Talks directly to Waze's own protocol, no login needed. Split from the mature, published waze-all-in-one-api for a focused, single-purpose workflow.

- **URL**: https://apify.com/romy/waze-sos-contacts-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 $2.30 / 1,000 sos contact chargeds

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 SOS Contacts Scraper do?

**Waze SOS Contacts Scraper** takes a batch of points (`{ lat, lon }`) and returns real local emergency numbers and roadside-assistance contacts for each one — police/ambulance/fire, AAA-style auto clubs, manufacturer roadside assistance — one dataset row per provider result.

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` in the source repo — field names and numbers are the real app's, not guesses). No Waze account, no API key, no scraping setup. This is the SOS-providers slice of [Waze All-in-One API](https://apify.com/romy/waze-all-in-one-api), split out as its own focused Actor.

### Why use Waze SOS Contacts Scraper?

- **Real local emergency and roadside-assistance data** — not templated, sourced live per point from Waze's own SOS-providers service
- **Batch multiple points in one run** — no natural pagination for this data, so this Actor accepts an array of points and pushes one row per result item
- **Global** — not tied to one country's data
- **No account needed** — every request mints its own short-lived anonymous session server-side; you never see or manage credentials
- **Use cases:** travel/safety apps, roadside-assistance directories, insurance/fleet risk tooling, emergency-contact enrichment for logistics and dispatch platforms

### How it connects to the parent

This Actor is a narrow, batch-run spin-off of [Waze All-in-One API](https://apify.com/romy/waze-all-in-one-api) (a Standby REST API), derived from its `GET /sos-providers` endpoint. Where the parent serves one HTTP request at a time with no dataset output, this Actor takes a JSON array of points as run input and pushes every provider found to the Apify dataset — suited to batch/offline lookups rather than live request/response integrations. It copies the parent's session/handshake logic (`src/waze-client.ts`, `src/waze-protobuf.ts`, `proto/waze_rt.proto`) verbatim, since Waze's protocol requires an identical 3-step login → register → signin handshake before any data call.

### Input

| Field    | Type  | Description                                                          |
| -------- | ----- | -------------------------------------------------------------------- |
| `points` | array | Required, non-empty array of `{ lat: number, lon: number }` objects. |

Example:

```json
{
    "points": [
        { "lat": 40.758, "lon": -73.9855 },
        { "lat": -6.1754, "lon": 106.827 }
    ]
}
```

### Output

One dataset row per SOS provider found, tagged with the originating point. Real response (trimmed, NYC):

```json
{ "point": { "lat": 40.758, "lon": -73.9855 }, "phone": "911", "name": "911" }
```

```json
{ "point": { "lat": 40.758, "lon": -73.9855 }, "type": 1, "subtype": 3, "phone": "18444110791", "name": "AAA" }
```

| Field                    | Description                                       |
| ------------------------ | ------------------------------------------------- |
| `point`                  | Echoes back the `{ lat, lon }` this row came from |
| `name` / `phone` / `url` | Contact details, as reported                      |
| `type` / `subtype`       | Numeric category (not yet mapped to a name)       |

A point that returns zero providers pushes no rows for that point (logged, not an error).

### Known limitations

- `type` / `subtype` are numeric Waze categories not yet mapped to human-readable names.
- This is an unofficial, reverse-engineered integration, not affiliated with or endorsed by Waze / Google. Behavior may change if Waze changes its protocol.
- For live route calculation, place search, nearby POI, alerts, and other Waze data, see the parent [Waze All-in-One API](https://apify.com/romy/waze-all-in-one-api).

### Pricing

Pay per event: **$0.003** per `sos-contact` — charged once for each SOS/roadside-assistance provider returned for a point (Free plan price; lower on paid Apify plans). See the Actor's Pricing tab for current tiered rates.

Found a bug or have a feature request? Use the Issues tab on this Actor's page.

# Actor input Schema

## `points` (type: `array`):

Array of { lat, lon } points to query. At least one point is required.

## Actor input object example

```json
{
  "points": [
    {
      "lat": 40.758,
      "lon": -73.9855
    }
  ]
}
```

# 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 '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "points": [
        {
            "lat": 40.758,
            "lon": -73.9855
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("romy/waze-sos-contacts-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 '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "points": [{
            "lat": 40.758,
            "lon": -73.9855,
        }] }

# Run the Actor and wait for it to finish
run = client.actor("romy/waze-sos-contacts-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 '{
  "points": [
    {
      "lat": 40.758,
      "lon": -73.9855
    }
  ]
}' |
apify call romy/waze-sos-contacts-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,romy/waze-sos-contacts-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 <APIFY_API_TOKEN>` 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/3G7X6RS8TWOdUPQhu/builds/FnP7jY9aXdGwJUcX2/openapi.json