# Roaming Hunger Food Truck Scraper — Leads, Cuisines & Contacts (`scrapersdelight/roaminghunger-scraper`) Actor

Scrape Roaming Hunger food trucks & mobile caterers by city — name, cuisine tags, rating, bookings, website, Instagram/Facebook & menus. Every US city on the site. Monitor mode alerts on new trucks. No login or API key. $4 per 1,000 trucks.

- **URL**: https://apify.com/scrapersdelight/roaminghunger-scraper.md
- **Developed by:** [Scrapers Delight](https://apify.com/scrapersdelight) (community)
- **Categories:** Automation, Lead generation, Agents
- **Stats:** 4 total users, 0 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per event

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#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

## 🚚 Roaming Hunger Food Truck Scraper — Leads, Cuisines & Contacts

**Build food-truck and mobile-caterer lead lists in minutes. Pick a city — any of the hundreds Roaming Hunger covers — and this actor pulls every listed truck with its public **website, Instagram, Facebook, Twitter, and Yelp**, plus **cuisine tags, average rating, review and booking counts**, the menu URL, and the truck's full service fleet (truck/cart, service radius, cost per mile). Run it on a schedule to catch **new** trucks as they list. The cleanest food-truck lead source on Apify.**

No login, no API key, no browser rendering. Roaming Hunger serves all of this from a fast public JSON backend, so runs are quick and reliable.

***

### Why this one

Roaming Hunger is the largest US food-truck & mobile-catering marketplace (~300–400 trucks per major city), and no other Apify actor covers it:

- ✅ **Website + Instagram + Facebook + Twitter + Yelp** are public on the listings
- ✅ **Cuisine tags** (Mexican, Tacos, BBQ, Coffee, …) and **average rating + review count** per truck
- ✅ **Booking activity** — total, catering, and vending bookings (a real "is this vendor active?" signal)
- ✅ **Service fleet** — truck vs. cart vs. drop-off, free miles, max miles, cost per mile, minimums
- ✅ A **new-truck monitor** with Slack / email / webhook alerts — watch any city for new vendors

***

### What you get (per truck)

`name` · `cuisines` · `city` / `city_display_name` / `state` · **`average_rating`** · `total_reviews` · **`total_bookings`** (+ catering/vending split) · **`website`** · **`instagram`** · `facebook` · `twitter` · `yelp` · `menu_url` · `level` · `verified` · `description` · `ranking_tier` · `instant_book` · `service_types` · `services` (radius + cost per mile) · `first_service_date` · `profile_url` · `is_new` · `scraped_at`

Export to CSV/JSON/Excel or pull via the Apify API into your CRM, Clay, n8n, or Make.

***

### How to use it

1. Click **Try for free**.
2. Enter one or more **cities** — slugs like `austin-tx`, `denver-co`, `los-angeles-ca` (see the full list at [roaminghunger.com/food-trucks](https://roaminghunger.com/food-trucks/)) or just `Austin, TX`.
3. Set **Max trucks** (0 = everything in the city).
4. Click **Start**, then open the **Dataset** tab.
5. **For a live feed:** turn on **Monitor mode** + an Apify **Schedule** to get alerted when new trucks list in your cities.

#### Quick start

```json
{ "cities": ["austin-tx"], "maxItems": 50 }
```

#### Full-city pull, multiple cities

```json
{ "cities": ["austin-tx", "denver-co", "san-antonio-tx"], "maxItems": 0 }
```

#### Daily new-truck monitor

```json
{ "cities": ["austin-tx"], "maxItems": 0, "monitorMode": true, "slackWebhookUrl": "https://hooks.slack.com/services/…" }
```

### Input

| Field | Type | Default | What it does |
|-------|------|---------|--------------|
| `cities` | array | `["austin-tx"]` | City slugs (`austin-tx`) or `"Austin, TX"` — one per entry |
| `maxItems` | integer | `50` | Total cap across all cities; `0` = unlimited |
| `enrichDetails` | boolean | `true` | Per-truck call adding cuisines, rating, bookings, fleet |
| `concurrency` | integer | `8` | Parallel enrichment fetches |
| `monitorMode` | boolean | `false` | Output/alert only trucks not seen in prior runs |
| `alertOnNewTruck` | boolean | `true` | Alert per new truck (monitor mode) |
| `webhookUrl` / `slackWebhookUrl` / `emailRecipients` | — | — | Where new-truck alerts go |
| `proxyConfiguration` | object | Apify proxy | Datacenter rotation is plenty |

### Output example

```json
{
  "name": "Tacoman512",
  "cuisines": ["Mexican", "Tacos", "Savory", "Breakfast"],
  "city": "austin-tx",
  "city_display_name": "Austin, TX, USA",
  "state": "TX",
  "average_rating": 4.98,
  "total_reviews": 53,
  "total_bookings": 289,
  "total_catering_bookings": 240,
  "total_vending_bookings": 49,
  "website": "www.Tacoman512.com",
  "instagram": "Instagram.com/Tacoman512",
  "facebook": "Facebook.com/Tacoman512",
  "level": 5,
  "verified": true,
  "service_types": ["truck", "dropoff", "traditional", "cart"],
  "services": [{ "type": "truck", "name": "Food truck", "free_miles": 40, "max_miles": 300, "cost_per_mile": 1.5, "included_hours": 2 }],
  "profile_url": "https://roaminghunger.com/tacoman512/",
  "record_id": "roaminghunger-30164",
  "source": "Roaming Hunger",
  "scraped_at": "2026-06-12T19:00:00.000Z"
}
```

***

### Who it's for

- 🍽️ **Food & beverage suppliers** selling to food trucks (ingredients, packaging, POS)
- 🏢 **Event planners & venues** sourcing mobile caterers by cuisine and rating
- 📣 **Agencies & lead-gen** building hospitality outreach lists with live social handles
- 🚚 **Food-truck marketplaces & SaaS** tracking vendor supply per city

***

### Pricing (pay-per-event)

| Event | What it covers | Price |
|-------|----------------|-------|
| `lot-scraped` | each truck/caterer returned | $0.004 (≈ $4 / 1,000) |
| `lot-detail-enriched` | each truck enriched with cuisines + rating + bookings | $0.004 |
| `monitor-run-completed` | each scheduled watch run | $0.05 |
| `new-lot-detected` | each newly listed truck | $0.02 |
| `alert-delivered` | each Slack/email/webhook alert | $0.005 |

***

### Monitor & alert setup

1. Run once with your cities + `monitorMode: true` (the first run baselines every existing truck).
2. Create an Apify **Schedule** (e.g. daily) for the same input.
3. Add a `slackWebhookUrl`, `webhookUrl`, and/or `emailRecipients` — each subsequent run outputs and alerts **only new trucks**. State persists in a named key-value store, so nothing is double-reported.

***

### Notes

- **Public directory data.** Names, websites, and social handles are public on Roaming Hunger. **You are responsible** for compliant outreach — follow **CAN-SPAM / GDPR / CASL**.
- **Coverage:** every city Roaming Hunger lists (hundreds across the US) — find slugs at `roaminghunger.com/food-trucks/`.
- **No double-counting** — a truck serving multiple cities is emitted once per run, and monitor mode remembers what it has seen.

***

### FAQ

**Do I need a Roaming Hunger account or API key?** No — the data is public and the actor needs no login or key.

**How current is the data?** It's read live from the same backend the Roaming Hunger site itself uses, on every run.

**How do I find my city's slug?** Open [roaminghunger.com/food-trucks](https://roaminghunger.com/food-trucks/) — every city page is `/food-trucks/<slug>/` (e.g. `austin-tx`). Or just enter `"Austin, TX"` and the actor converts it.

**What does `enrichDetails` add?** Cuisine tags, average rating, review count, booking counts (total / catering / vending), the full description, and the service fleet with radius + cost per mile. Turn it off for a faster contacts-only pull.

**Does it get phone numbers or emails?** Roaming Hunger doesn't expose phones/emails publicly — you get website + Instagram + Facebook + Twitter + Yelp, which is what's public. Pair the `website` field with an email-enrichment actor for inboxes.

**Can I scrape multiple cities in one run?** Yes — add as many slugs as you like to `cities`; `maxItems` caps the combined total (set `0` for everything).

**What's `total_bookings`?** The number of bookings the truck has done through Roaming Hunger — a strong signal of an active, revenue-generating vendor.

**What's `level`?** Roaming Hunger's own 1–5 quality score for the listing.

**How does monitor mode avoid duplicates?** Seen truck IDs are stored per city-set scope in a named key-value store that persists across runs; only unseen IDs are output/alerted.

**Is this legal?** It collects publicly displayed business-directory data. Review Roaming Hunger's terms and your local laws; you are responsible for how you use the data.

# Actor input Schema

## `cities` (type: `array`):

City slugs from roaminghunger.com/food-trucks/ (e.g. austin-tx, denver-co, los-angeles-ca) — or just type 'Austin, TX'. One entry per city.

## `maxItems` (type: `integer`):

Cap on total trucks across all cities. Set 0 for unlimited (a major city has ~300-400 trucks).

## `enrichDetails` (type: `boolean`):

One extra API call per truck adds cuisine tags, average rating, review/booking counts, description, and the service fleet (truck/cart, service radius, cost per mile).

## `concurrency` (type: `integer`):

How many detail enrichments to run in parallel.

## `monitorMode` (type: `boolean`):

Recurring watcher: diff against the prior run (per city set) and output/alert ONLY new trucks. Pair with an Apify Schedule.

## `alertOnNewTruck` (type: `boolean`):

In monitor mode, send an alert for each newly listed truck.

## `webhookUrl` (type: `string`):

POST endpoint for new-truck alerts.

## `slackWebhookUrl` (type: `string`):

Slack incoming-webhook URL.

## `emailRecipients` (type: `array`):

Emails for the new-truck digest (via apify/send-mail).

## `proxyConfiguration` (type: `object`):

Proxy settings. Datacenter rotation is plenty (the API only checks the User-Agent).

## `diagnose` (type: `boolean`):

Dev only. Logs the first parsed truck (enriched), then exits.

## Actor input object example

```json
{
  "cities": [
    "austin-tx"
  ],
  "maxItems": 50,
  "enrichDetails": true,
  "concurrency": 8,
  "monitorMode": false,
  "alertOnNewTruck": true,
  "proxyConfiguration": {
    "useApifyProxy": true
  },
  "diagnose": false
}
```

# Actor output Schema

## `trucks` (type: `string`):

The dataset of food trucks & mobile caterers (one item per truck).

# 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 = {
    "cities": [
        "austin-tx"
    ],
    "maxItems": 50
};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapersdelight/roaminghunger-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 = {
    "cities": ["austin-tx"],
    "maxItems": 50,
}

# Run the Actor and wait for it to finish
run = client.actor("scrapersdelight/roaminghunger-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"])
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "cities": [
    "austin-tx"
  ],
  "maxItems": 50
}' |
apify call scrapersdelight/roaminghunger-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=scrapersdelight/roaminghunger-scraper",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/mBmWMaQ9twlo7clHH/builds/twq2xoIsr5wVcKX0f/openapi.json