# Event Vendor Leads Scraper — 4 Sites, One List (`scrapersdelight/event-vendor-leads-scraper`) Actor

Event vendor leads from The Bash, Eventective, BounceGuide and Roaming Hunger in one run: DJs, caterers, photographers, food trucks, bounce houses and more, with rating, price band, phone, website and a contact email crawled from the vendor's own site.

- **URL**: https://apify.com/scrapersdelight/event-vendor-leads-scraper.md
- **Developed by:** [Scrapers Delight](https://apify.com/scrapersdelight) (community)
- **Categories:** Lead generation, Business, Travel
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$4.00 / 1,000 per vendor returneds

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/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

## 🎪 Event Vendor Leads Scraper — four marketplaces, one lead list

Pick a **category** and a **city** and get one clean list of event vendors — DJs, caterers,
photographers, food trucks, bounce-house rentals and more — pulled from **The Bash, Eventective,
BounceGuide and Roaming Hunger** at once, de-duplicated, and — for the sources that publish a vendor
website (Eventective, BounceGuide, Roaming Hunger) — enriched with a **contact email crawled from the
vendor's own site**. The Bash gates every contact detail behind its own lead form and publishes no
vendor website, so The Bash rows carry no email: a DJ, band, bartender, comedian, magician or
photo-booth run, which only The Bash serves, returns marketplace rows without emails.

One run instead of four. One row shape instead of four.

### What does this actor do?

- 🎧 **`name`, `category`, `city`, `state`** — the vendor and where they work
- ⭐ **`rating`, `reviewCount`, `bookings`, `verified`** — social proof where the source publishes it
- 💵 **`priceFrom` / `pricePeriod`** — starting price where listed
- 📞 **`phone`** and 🌐 **`website`** — published by Eventective, BounceGuide and Roaming Hunger;
  The Bash publishes neither for talent listings
- 📧 **`email`, `emailType`, `additionalEmails`** — crawled from the vendor's own site, so only on
  rows that carry a website
- 🔗 **`profileUrl`** and **`source`** — so every row traces back to where it came from

### Example input

```json
{
  "category": "caterer",
  "location": "Austin, TX",
  "findEmails": true,
  "requireEmail": true,
  "maxItems": 200
}
```

### Which marketplace covers which category

The four sites do not overlap much, and asking one for a category it does not list just returns
nothing. So for every category in the list below the actor routes to the sources that actually serve
it, and the log names the ones it skipped. Use a category from that list: an unrecognised one is sent
to all four sources, and BounceGuide and Roaming Hunger ignore the category entirely, so you will be
charged for bounce houses and food trucks you did not ask for.

| Category | Searched on |
|---|---|
| dj, band, bartender, comedian, magician, photo booth | The Bash |
| photographer, videographer, caterer | The Bash + Eventective |
| florist, planner, entertainer, officiant, venue, wedding venue | Eventective |
| food truck | Roaming Hunger |
| bounce house | BounceGuide |

**Measured 2026-08-23:** Eventective 404s on 6 of the 15 categories it advertises
(disc-jockeys, bands-musicians, party-event-rentals, limousine-services, cakes-desserts,
photo-booth-rentals). Three of those six — disc-jockeys, bands-musicians and photo-booth-rentals —
are served by The Bash instead. The other three (party rentals, limousines, cakes and desserts) are
not offered by this actor: pass a category from the list above, because an unrecognised category is
not routed and the category-blind sources (BounceGuide, Roaming Hunger) will return bounce houses and
food trucks for it.

### The email hop, and what it honestly yields

Vendor marketplaces gate contact details behind their own quote forms — that is their business
model. So this actor takes the vendor's **website** and crawls a few pages of it (home, contact,
about) for a published address.

From a real Austin caterer run: 16 vendors, of which the **10 Eventective rows carried a vendor
website and 6 of those 10 yielded a usable email** — the rest publish only a contact form. The 6 The
Bash rows carry no website, so they are never crawled.

**A found address must actually belong to the business.** Crawling a website returns every address
on the page, including other people's. In testing, "FIORE CATERING & EVENTS" came back with
`jonpinhorn.typedesign@gmail.com` — a font designer credited in the site's CSS. Shipping that as the
caterer's contact is worse than shipping nothing, so an address is only accepted when it is on the
vendor's own domain, is a generic role mailbox (`info@`, `hello@`, `bookings@`), or its local part
shares a real word with the business name. Rejected sites are counted in the run log.

`emailType` tells you what you got: `role` (info@, bookings@), `personal`, or `other`.

### Who is this for?

Event-tech and booking SaaS selling to vendors, wedding and event marketplaces building supply,
equipment and insurance vendors, and agencies doing local event-market research.

### Honest limits

- **Coverage varies by city.** An Austin caterer search returns roughly 15-25 vendors; small towns
  return a handful. Raise `maxItems` (default 100) if a large metro has more.
- **Not every vendor has a website**, and not every website publishes an address. Set `requireEmail`
  if you only want contactable rows — you are not charged for the ones dropped.
- **De-duplication is by website domain**, falling back to name + city. A vendor listing on two
  marketplaces under slightly different names can survive as two rows.
- **The Bash sits behind Akamai.** The default Apify proxy (auto) worked in testing; switch to
  residential if you see blocks on very large runs.
- **The four single-site actors remain available** if you only want one source.

### Pricing

| What | Price |
|---|---|
| Per vendor returned | **$0.004** |

Filtered rows cost nothing.

### FAQ

**Can I run every category at once?**
Run one category per run — that is how the marketplaces organise their listings.

**Why did it only search one site?**
Because only one of them lists that category. The log names the skipped sources.

**How long does a run take?**
Without email crawling, seconds. With it, budget a few seconds per vendor website.

**Can I get more vendors from a city?**
Raise `maxItems`. The cap is spread across the sources that serve your category. For Eventective
also raise `maxPagesPerSite`, which caps how many listing pages it reads (default 4) as well as how
deep each vendor site is crawled for an email.

**Is the email verified?**
It is published on the vendor's own site and checked for plausibility against the business, but not
deliverability-tested. Run it through a verifier if that matters.

**What if a vendor has no website?**
You still get the marketplace row — category, city, rating and phone where the source lists them,
and the profile URL.

**Do you scrape the marketplaces' own contact forms?**
No. Contact details come from the vendor's own public website, not from behind any gate.

**Which sources can I force?**
Pass `sources` with any of `thebash`, `eventective`, `bounceguide`, `roaminghunger`.

### Data source and fair use

Rows come from public marketplace listing pages and from vendors' own public websites. No login,
no paywall and no quote form is used. You are responsible for lawful outreach — CAN-SPAM and
equivalent rules apply to what you send, not to the data.

# Actor input Schema

## `category` (type: `string`):

One category: dj, band, photographer, videographer, caterer, bartender, comedian, magician, photo booth, florist, planner, entertainer, officiant, venue, wedding venue, food truck, bounce house. Only the marketplaces that actually list that category are searched.

## `location` (type: `string`):

City and state, e.g. "Austin, TX". Larger metros return more vendors.

## `sources` (type: `array`):

Limit to specific sources: thebash, eventective, bounceguide, roaminghunger. Leave empty to use every source that covers your category.

## `findEmails` (type: `boolean`):

Crawl each vendor's own website for a contact address. This is the slow part of a run — turn it off for a fast vendor list.

## `requireEmail` (type: `boolean`):

Drop vendors with no verifiable contact address. Dropped rows are not charged.

## `requireWebsite` (type: `boolean`):

Drop vendors that list no website.

## `maxPagesPerSite` (type: `integer`):

How many pages of each vendor's site to check for an email (home, contact, about...). Higher finds more, costs more time.

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

Parallel requests. Keep modest to stay polite with the marketplaces.

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

Stop after this many vendors. 0 = unlimited.

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

The Bash sits behind Akamai; Apify datacenter rotation worked in testing. Switch to residential if you see blocks at scale.

## Actor input object example

```json
{
  "category": "caterer",
  "location": "Austin, TX",
  "sources": [],
  "findEmails": true,
  "requireEmail": false,
  "requireWebsite": false,
  "maxPagesPerSite": 4,
  "concurrency": 5,
  "maxItems": 20,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

## `vendors` (type: `string`):

The dataset of scraped vendors.

# 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 = {
    "category": "caterer",
    "location": "Austin, TX",
    "findEmails": false,
    "maxItems": 20
};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapersdelight/event-vendor-leads-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 = {
    "category": "caterer",
    "location": "Austin, TX",
    "findEmails": False,
    "maxItems": 20,
}

# Run the Actor and wait for it to finish
run = client.actor("scrapersdelight/event-vendor-leads-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 '{
  "category": "caterer",
  "location": "Austin, TX",
  "findEmails": false,
  "maxItems": 20
}' |
apify call scrapersdelight/event-vendor-leads-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,scrapersdelight/event-vendor-leads-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/905ORlXIBQ5PtqH5k/builds/4baBjizQd93bLxiXw/openapi.json