The Knot Couples Scraper

The Knot Couples Scraper

Scrape The Knot wedding couples by name or discover them in bulk without any name. Every couple comes with both partner names, wedding date, location, and their public registry URL. No login or API key. Export to CSV, JSON, Excel, or XML.

The Knot's public wedding websites are a rich source of engaged couples, but there is no official API for couple data. This Actor reads the public couple pages directly, either by searching a known first and last name or by walking public couple IDs in Discover mode. You get a clean dataset of couples with their wedding details, ready for outreach or market research.

Who uses it	What they scrape The Knot for
Wedding vendors	Build a list of engaged couples in their service area to offer photography, catering, or planning services.
Market researchers	Analyze wedding trends by location, date, and couple demographics across the US.
Lead generation agencies	Deliver fresh, targeted couple leads to clients in the wedding industry.
Event planners	Find couples planning weddings in specific months or states to pitch their services.

What it does

This Actor collects The Knot wedding couples by name search or bulk ID discovery, and returns each couple as a flat row with partner names, wedding date, location, and registry URL.

• 🔍 Search by name: Enter a first and last name to find matching couples, with optional wedding month and year filters.
• 🧭 Discover couples: Walk public couple IDs in bulk without any name, starting from a chosen ID or a random point near the live frontier.
• 📍 Location filter: Keep only couples in a specific US state using a 2-letter code or full state name, applied before full-page fetch.
• 📅 Date range filter: Filter discovered couples by wedding date from and to, at month granularity.
• ✅ Complete leads only: Optionally skip sparse records and keep only couples with both names, a public date, and a city or state.

Results export to CSV, JSON, Excel, or XML, or straight from the API.

What you can do with The Knot data

📈 Build a targeted vendor outreach list.

A wedding photographer in Texas runs Discover mode with the US State filter set to TX and a date range for the next 12 months, then exports the couples to a CSV for a direct mail campaign.

🔎 Find a specific couple's wedding details.

A gift buyer searches by the couple's first and last name to retrieve their wedding date, location, and registry URL before purchasing a present.

📊 Analyze wedding season trends.

A market researcher runs Discover mode across multiple states and months to count weddings by region and season, then visualizes the data in a spreadsheet.

🎯 Generate fresh leads for a wedding planning service.

A lead generation agency schedules weekly Discover runs with Only complete leads enabled, delivering a clean list of engaged couples to their CRM.

Why choose this scraper

	What you get
No official API	The Knot does not offer a public API for couple data; this Actor reads the public pages directly.
Bulk discovery	Discover mode enumerates couples by ID without needing any names, so you can collect thousands of leads.
Clean, flat output	Each couple is returned as a single row with consistent fields, ready for CSV, JSON, Excel, or XML export.
Fast pre-filters	State and date filters are applied from the couple's public URL before the full page is fetched, saving time and resources.

How it compares

This Actor focuses on wedding couples, while the competitors below scrape wedding vendors from The Knot and other sites.

Feature	ParseForge	Wedding Vendor Scraper - 7 Sites	Wedding Vendor Aggregator Scraper (The Knot + WeddingWire)	The Knot Marketplace Scraper
Scrapes wedding couples	Yes	Not listed	Not listed	Not listed
Search by couple name	Yes	Not listed	Not listed	Not listed
Bulk discovery without names	Yes	Not listed	Not listed	Not listed
Wedding date and location filters	Yes	Not listed	Not listed	Not listed
Scrapes wedding vendors	Not listed	Yes	Yes	Yes
Vendor contact info (phone, email)	Not listed	Yes	Yes	Yes
Vendor reviews and ratings	Not listed	Yes	Yes	Yes

Configure the run

Drive the Actor with a name search or bulk ID discovery, and apply filters for state, wedding date range, and completeness so only relevant couples reach your dataset. The Input tab lists every parameter.

A first run with the defaults:

{
 "firstName": "Jessica",
 "lastName": "Miller",
 "maxScan": 3000,
 "maxItems": 10
}

A larger pull:

{
 "firstName": "Jessica",
 "lastName": "Miller",
 "maxScan": 3000,
 "maxItems": 200
}

Pricing

Pay-per-result: $0.006 per result collected. You pay only for the results written to your dataset.

Results collected	Approximate cost
100 results	$0.60
1,000 results	$6.00
10,000 results	$60.00

New Apify accounts start with $5 in free credit.

Free users

Free-plan runs return up to 10 results as a preview. Upgrade your Apify plan to collect up to 1,000,000 results per run.

Run it

1. Create a free Apify account with $5 in credit.
2. Open the The Knot Couples Scraper.
3. Set your inputs and any filters, then click Start.
4. Export the results as CSV, Excel, JSON, or XML from the Dataset tab.

Run it programmatically through the Apify API (run-sync-get-dataset-items) or the ApifyClient for JavaScript and Python.

Use with AI agents (MCP)

Give an AI agent live access to The Knot through the Model Context Protocol. Add the Actor to Claude, Cursor, or any MCP client:

$claude mcp add --transport http apify "https://mcp.apify.com?tools=parseforge/theknot-couples-scraper"

Then prompt it in plain language to run the scraper and read back the results.

Troubleshooting

Why am I getting no results in Search mode?

Make sure you entered both a first and last name, each at least 2 characters. The Knot requires both to return search results. Also check that your optional month and year filters are not too restrictive.

Why does Discover mode return fewer couples than expected?

Check your filters: US State, wedding date range, and 'Only complete leads' can all reduce the output. Also ensure 'Max IDs to scan' is high enough to cover the ID range you are probing.

Why do some couples have blank fields?

Some couples have sparse public pages. Enable 'Only complete leads' to skip those records, or adjust your filters to target more complete profiles.

Why does the run stop before reaching 'Maximum couples'?

The 'Max IDs to scan' budget may have been exhausted. Increase it if you want the Actor to probe more IDs, or broaden your filters to find more matches per ID.

Can I get couples from a specific city, not state?

The current filter is at the state level only. You can post-filter the exported dataset by city using your own tools, or contact support to request city-level filtering.

FAQ

Question	Answer
Do I need a The Knot account or API key?	No. The Actor reads public couple pages directly and does not require any login, registration, or API key.
What is the difference between Search and Discover mode?	Search mode requires a first and last name and returns matching couples. Discover mode walks public couple IDs in bulk without any name, so you can collect many couples at once.
Can I filter by wedding date?	Yes. In Discover mode you can set a wedding date from and to (month granularity). In Search mode you can filter by wedding month and year.
How does the US State filter work?	It accepts a 2-letter code like WA or a full name like Washington. The filter is applied to the couple's public URL before the full page is fetched, so it is fast and cheap.
What does 'Only complete leads' do?	When enabled, the Actor keeps only couples that have both partner names, a public wedding date, and a city or state. Incomplete couples are counted in the log but not returned.
How many couples can I collect per run?	You set the maximum with the 'Maximum couples' input, up to 1,000,000. The default is 10.
What is the 'Max IDs to scan' setting?	In Discover mode, this is a safety budget that limits how many couple IDs the Actor will probe in one run. It prevents a narrow filter from scanning forever.
Can I start discovery from a specific couple ID?	Yes. Set the 'Start Couple ID' input to begin walking IDs downward from that number. If left blank and 'Randomize start' is on, each run starts at a random point in the populated band.
What data do I get for each couple?	Each row includes both partner names, wedding date, location (city and state), and the couple's public registry URL, among other fields.
Is this legal to scrape?	You should only scrape public data in accordance with The Knot's terms of service and applicable laws. This Actor does not bypass any login or paywall.

Related actors

Browse the full ParseForge collection for more scrapers.

🆘 Need help? Email parseforge@protonmail.com with your run ID, your input, and what you expected.

⚠️ Disclaimer. This Actor is unofficial and is not affiliated with, endorsed by, or sponsored by The Knot Worldwide Inc. It collects only publicly available data. You are responsible for using the collected data in compliance with the source's terms of service and applicable data-protection laws, including GDPR, CCPA, and PIPL. Do not use it to collect personal data unlawfully.