Bridebook Scraper — Wedding Venues, Suppliers & Leads (Emails, Phones & Prices)

Disclaimer: This Actor is an independent tool and is not affiliated with, endorsed by, or sponsored by Bridebook or any of its subsidiaries. All trademarks mentioned are the property of their respective owners. "Bridebook" is referenced only to describe the publicly available website this Actor collects data from.

Extract complete wedding-vendor data from Bridebook — venues and every supplier type (photographers, caterers, florists, cakes, bands & DJs, planners, hair & makeup, bridalwear, transport, stationery, and more) — with the fields other scrapers leave empty: direct contact email, phone number, website, Instagram / Facebook / TikTok / Pinterest / LinkedIn, exact price ranges, capacity, reviews, full address & geo, and the venue/business manager's name.

Every record is a ready-to-contact lead. No login, no cookies, no browser — fast JSON extraction with high reliability across 11 countries (UK, Ireland, Australia, Canada, New Zealand, South Africa, Germany, Austria, Switzerland, France, Poland).

Why this Bridebook scraper?

The big wedding directories (The Knot, WeddingWire, Zola) are locked behind aggressive anti-bot walls, so most "wedding vendor" scrapers are slow, flaky, and return little more than a name and a star rating. This actor pulls the full vendor record Bridebook itself uses and ships the richest wedding-vendor dataset in the category:

Data	Typical scrapers	This actor
Direct contact email	❌	✅
Phone number	❌ partial	✅
Website + Instagram / Facebook / TikTok / Pinterest / LinkedIn	❌	✅
Exact price range (from / to) + per-head + total-inclusive	❌	✅
Reviews count, star rating, testimonials	partial	✅
Capacity, accommodation, team size, weddings hosted	❌	✅
Manager / owner name	❌	✅
Full address, postcode, lat/lng	partial	✅
Specialties (Asian, Jewish, Muslim, LGBTQ+, multi-faith…)	❌	✅
Style, services & amenities (per vendor type)	❌	✅
Lead score (0–100)	❌	✅
All venues and all supplier types in one actor	❌	✅

Use cases

• Wedding-industry lead generation — venues and suppliers are active buyers and partners. Reach them directly with verified email, phone, website and socials, scored 0–100 by leadScore. Perfect for wedding SaaS/CRMs (booking, planning, payments), insurance, supply & rental brands, photographers/planners looking for partner vendors, and marketing agencies serving the wedding niche.
• Market & pricing intelligence — benchmark venue hire and supplier prices (priceFrom, priceTo, pricePerHeadMin, pricingIndicator) by city, county, country and category.
• Vendor directories & lead-gen sites — power your own wedding marketplace, county guides, or newsletters with structured, photo-rich vendor data.
• Competitor & partner mapping — find every photographer, caterer or florist in a region, with reviews, weddings hosted and specialties.
• Monitoring — schedule recurring runs and capture only new or changed vendors (price drops, new reviews, fresh listings) for a continuously updated lead feed.

How to use

1. Sign up for Apify — the free plan is enough to try this actor.
2. Open the Bridebook Scraper, choose your categories (e.g. venues, photographers), locations (e.g. london, manchester), and a market (country) — or paste Bridebook URLs into Start URLs — and click Start.
3. Watch vendor leads stream into the dataset table.
4. Export as JSON, CSV, Excel, XML, or RSS — or pull results via the Apify API.

Input

{
    "categories": ["venues", "photographers"],
    "locations": ["london", "kent"],
    "market": "uk",
    "maxResults": 200,
    "includeVendorDetails": true,
    "enrichContactEmails": false,
    "monitorMode": false
}

• categories — wedding vendor types, combined with every location: venues, photographers, videographers, catering, florists, cakes, music (bands & DJs), planners, beauty (hair & makeup), bridalwear, menswear, jewellery, transport, stationery, marquee, entertainment, decoration.
• locations — towns, cities, regions or counties (london, manchester, edinburgh, kent, yorkshire). Match them to your market.
• market — country site: uk, ie, au, ca, nz, za, de, at, ch, fr, pl.
• startUrls — direct Bridebook URLs: vendor profiles (/uk/wedding-venues/...) or search/listing pages (/uk/search/wedding-photographers/london).
• maxResults — cap on total vendor records.
• Filters — minReviews, minRating, maxPrice, hasEmailOnly, hasPhoneOnly, hasWebsiteOnly.
• includeVendorDetails (default true) — fetch the full vendor record: direct email, phone, website, all socials, full address & geo, description, exact price range, capacity, team size, manager name, weddings hosted, insurance, inclusivity options and specialties. This is the lead-gen wedge.
• enrichContactEmails (default false) — additionally crawl the vendor's own website (home + contact/about, max 3 pages) for extra emails, phones and social links.
• monitorMode (default false) — remember vendors from previous runs and output only those that are new or changed; each record is tagged with changeType.

Output

One clean record per wedding vendor (type: "vendor"):

{
    "type": "vendor",
    "publicId": "csmgbq6lNX",
    "supplierId": "CS00348023",
    "name": "Clapton Country Club",
    "vendorType": "Venue",
    "market": "uk",
    "country": "GB",
    "currency": "GBP",
    "city": "London",
    "county": "Greater London",
    "customArea": "East London",
    "postcode": "E5 0RT",
    "addressFull": "Clapton, London, E5 0RT",
    "latitude": 51.561,
    "longitude": -0.056,
    "reviewsStars": 5,
    "reviewsCount": 11,
    "testimonialsCount": 4,
    "photosCount": 42,
    "weddingsHosted": 120,
    "pricingIndicator": "$$",
    "priceFrom": 4550,
    "priceTo": 9150,
    "pricePerHeadMin": 85,
    "capacityDining": 120,
    "teamSize": 14,
    "hasInsurance": true,
    "inclusivityOptions": ["lgbtqPlusExpert", "multiFaith"],
    "managerName": "Terence",
    "tags": ["asian-weddings", "jewish-weddings"],
    "attributes": { "style": ["modern", "industrial"], "details": ["exclusiveUse", "outdoorSpace"] },
    "descriptionShort": "A relaxed, independent East London wedding venue…",
    "email": "terence@claptoncountryclub.com",
    "phone": "+442036693594",
    "website": "https://claptoncountryclub.com",
    "instagram": "https://instagram.com/claptoncountryclub",
    "facebook": "https://www.facebook.com/claptoncountryclub",
    "leadScore": 94,
    "profileUrl": "https://bridebook.com/uk/wedding-venues/clapton-country-club-london-greater-london",
    "searchCategory": "venues",
    "searchLocation": "london",
    "scrapedAt": "2026-06-16T16:00:00.000Z"
}

Supplier records (photographers, caterers, etc.) add exact priceFrom/priceTo, pricingDescription, and a type-specific attributes block (e.g. photographyStyle, productsServices).

How much does it cost to scrape Bridebook?

This Actor uses Apify's pay-per-event pricing: you are charged only for the results it delivers, with no monthly rental and no start fee. The events it can charge are:

• Vendor scraped - One vendor record from Bridebook Scraper - Wedding Venues, Suppliers & Leads in the default dataset — all extracted fields for this item, plus a derived lead score where applicable.
• Contact enriched - One contactEnrichment record from Bridebook Scraper - Wedding Venues, Suppliers & Leads in the default dataset — all extracted fields for this item, plus a derived lead score where applicable.

The current price of each event is shown on the Pricing tab of this page. Set a maximum total charge on the run if you want a hard cap on spend, and use the input limits to control how much the Actor fetches.

Automate & schedule

Run this actor on autopilot and pull results into your own stack:

• Apify API — start runs, fetch datasets, and manage schedules over REST.
• apify-client for JavaScript and apify-client for Python — official SDKs.
• Schedules — run it daily/weekly with monitorMode to capture only new or changed wedding vendors for a fresh lead pipeline.
• Webhooks — trigger downstream actions (CRM import, Slack alert, email sequence) the moment a run finishes.

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: 'MY_APIFY_TOKEN' });

const run = await client.actor('scrapesage/bridebook-scraper').call({
    categories: ['venues', 'photographers'],
    locations: ['london'],
    market: 'uk',
    maxResults: 200,
    includeVendorDetails: true,
});

const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(`Got ${items.length} wedding-vendor leads`);

Integrate with any app

Connect the dataset to 5,000+ apps — no code required:

• Make — multi-step automation scenarios.
• Zapier — push new wedding-vendor leads straight into your CRM.
• Slack — get notified when a monitored search finds new vendors.
• Google Drive / Sheets — auto-export every run to a spreadsheet.
• Airbyte — pipe results into your data warehouse.
• GitHub — trigger runs from commits or releases.

Use with AI assistants (MCP)

The output is clean, LLM-ready JSON. Call this actor from Claude, ChatGPT, or any agent framework through the Apify MCP server — ask your assistant to "find wedding venues in Kent under £6,000 with contact emails" and let it run this scraper for you.

Agent-ready: autonomous payments (x402 & Skyfire)

This actor is agent-ready — AI agents can discover it, run it, and pay for it autonomously, with no Apify account and no human in the loop. It uses pay-per-event pricing and limited permissions, so it qualifies for Apify's agentic-payment standards:

• x402 — an open, HTTP-native payment protocol. Agents pay per run in USDC on the Base network directly through the Apify MCP server — no account, no API key.
• Skyfire — agent-to-service payments for fully autonomous AI-agent workflows.

Building an AI agent, MCP tool, or autonomous data pipeline? This scraper is ready to plug in and pay as it goes.

More scrapers from scrapesage

Build a complete local-business & events lead-gen stack:

• Fresha Scraper — salon, spa & beauty business leads.
• Booksy Scraper — beauty & wellness provider leads.
• Eventbrite Scraper — events with ticket prices and organizer leads.
• Bark Listing Scraper — service-provider leads from Bark.
• Houzz Scraper — home pros, contacts and reviews.
• GetYourGuide Scraper — tours, activities, prices and reviews.
• Caring.com Senior Living Scraper — assisted-living facility leads.
• DesignRush Scraper — marketing, design & dev agency leads.

Tips

• Exhaust a big city: large markets cap at ~700+ venues per location. Split by category and/or by sub-region (e.g. london, then specific London areas) to go deeper.
• Stable monitoring: set maxResults high enough to cover a location — Bridebook rotates "boosted" suppliers in the top results, so a small cap with monitorMode will keep surfacing different vendors until the location is covered.
• Cost control: keep includeVendorDetails on (it's cheap — contacts come straight from Bridebook, no website crawl). Only turn on enrichContactEmails when you want extra emails beyond the one already provided.
• Proxies: the default Apify Proxy (datacenter) is verified clean and fast for Bridebook.

FAQ

How do I scrape wedding venues for a specific city? Put the city in locations (e.g. london, manchester, dublin) and venues in categories, then pick the matching market (country). Combine with supplier categories to pull photographers, caterers, florists and more in the same run.

Where do the emails and phone numbers come from? From the vendor's own public Bridebook listing data — the same contact details a couple would use to enquire. With enrichContactEmails on, the actor additionally visits the vendor's website for any extra emails.

Which countries are supported? UK, Ireland, Australia, Canada, New Zealand, South Africa, Germany, Austria, Switzerland, France and Poland — set the market field.

Can I export to Google Sheets, CSV, or Excel? Yes — one click in the dataset view, or automatically on every run via the Google Drive integration.

How do I get only new vendors automatically? Turn on monitorMode and create a Schedule. The scheduler decides when to run; monitor mode returns only new or changed vendors (tagged with changeType). They work together — no conflict.

Is scraping Bridebook legal? This actor collects publicly available data only. You are responsible for using the data in compliance with applicable laws (GDPR/CCPA for personal data) and Bridebook's terms.

A field is null — why? Some vendors genuinely don't publish a price, website, or capacity. Fields are null only when the data doesn't exist, not because the scraper skipped them.

Data & lawful use

This Actor reads business and professional listings that the professionals themselves published to be found: names, roles, firms, ratings and the contact details shown on the public listing. Because those details belong to identifiable people, treat the output as personal data. If you are in the EU or UK you are the data controller for what you do with it: have a lawful basis (usually legitimate interest for B2B prospecting or market research), keep any outreach relevant to the professional's line of work, honour opt-outs and deletion requests, and do not use the output for spam.

Under Apify's Standard Actor Contract, which governs your use of this Actor, you are the controller of any personal data in your input and output and scrapesage acts only as your processor: that data is processed solely to run your job, written only to your own Apify storage, never used for any other purpose and never shared onward. If you need help with a data-subject request that involves this Actor's output, open an issue on the Issues tab.

Disclaimer

This Actor is an independent tool and is not affiliated with, endorsed by, or sponsored by Bridebook or any of its subsidiaries. All trademarks mentioned are the property of their respective owners.

"Bridebook" and any related marks are the property of their respective owners and are used here only in a descriptive, nominative sense - to identify the publicly accessible website from which this Actor collects data. This Actor is not an official Bridebook product, is not authorised or certified by Bridebook, and does not distribute Bridebook software. It collects only publicly available information; you are responsible for ensuring your use of that data complies with applicable laws, regulations and the terms of the source website.

Need help?

Open an issue on the actor's Issues tab, or visit the Apify help center. Feature requests are welcome — this actor is actively maintained.