💍 The Knot Wedding Couple Enrichment Scraper

🚀 Turn a couple's name into their full public wedding profile in seconds. Input a first and last name, get back both partners, wedding date, city and state, venue, wedding website, and registry, up to 22 fields per record.

🕒 Last updated: 2026-07-08 · 📊 22 fields per record · public wedding-website data only · US, Canada and international couples

The Knot Wedding Couple Enrichment Scraper looks up the information a couple has already chosen to publish on their public The Knot wedding website and returns it as clean, structured data. You provide a first name and a last name (for example a guest, vendor, or planner who already knows the couple), and the Actor returns every matching public couple: both partners' names, the wedding date, the city and state, the venue (when the couple added it), the wedding website URL, and the gift registry URL.

This is an enrichment tool, not a discovery or contact-list tool. It does not browse or dump a directory of strangers. It resolves a name you already have into the public wedding details that The Knot itself displays on its open "Find a Couple" search, then structures them so you can drop them into a spreadsheet or CRM instead of copying by hand.

🎯 Target Audience	💡 Primary Use Cases
Wedding vendors (venues, photographers, planners, florists, caterers)	Confirm a lead's wedding date, location, and venue before quoting
Registry and gifting services	Match a known couple to their public registry link
Guests and travel planners	Find a couple's public wedding website and registry from a name
Wedding-industry analysts	Structure publicly published wedding details for market research

📋 What the Actor does

1. Takes a first name and last name (both required, minimum 2 characters each).
2. Queries The Knot's public "Find a Couple" search (theknot.com/registry/couplesearch).
3. Returns every matching public couple with both partners' names, wedding date, city, state, country, wedding website URL, and registry URL.
4. Optionally enriches each result with venue details (venue name, address, ceremony and reception locations) by reading the couple's own public wedding-website page. Venue is included only when the couple has filled it in.
5. Optional filters narrow results by wedding month and year.

🎬 Full Demo (🚧 Coming soon)

⚙️ Input

Field	Key	Type	Required	Description
Mode	mode	select (search / discover)	No	Default search. search looks up a name you already have; discover browses The Knot's public couple directory with optional filters.
First Name	firstName	string	✅ Yes (search mode)	First name of one partner (min 2 characters). Applies to search mode.
Last Name	lastName	string	✅ Yes (search mode)	Last name of one partner (min 2 characters). Applies to search mode.
Wedding Month	eventMonth	string (1-12)	No	Search mode filter. Use together with Wedding Year.
Wedding Year	eventYear	string	No	Search mode filter, for example 2026.
Start Couple ID	startCoupleId	integer	No	Discover mode only. Optional start point in the public couple space.
Randomize Start	randomizeStart	boolean	No	Discover mode only. Default true. Starts from a fresh point so each run sees different public couples.
US State	usState	string (2-letter)	No	Discover mode filter, for example TX.
Wedding Date From	weddingDateFrom	string	No	Discover mode filter, YYYY-MM-DD.
Wedding Date To	weddingDateTo	string	No	Discover mode filter, YYYY-MM-DD.
Max Scan	maxScan	integer	No	Discover mode only. Cap on how many public couple IDs the run walks (your scan budget).
Include venue details	includeVenue	boolean	No	Default true. Fetches each couple's public wedding-website page for venue details. Applies to both modes.
Only complete leads	onlyComplete	boolean	No	Default off. When on, keeps only couples that have both partner names, a wedding date, and a city or state; sparse records are skipped and counted in the run log rather than silently dropped.
Max Items	maxItems	integer	No	Free plan: 10. Paid: up to 1,000,000.

Example 1: basic name lookup with venue enrichment

{
    "firstName": "Jessica",
    "lastName": "Miller",
    "includeVenue": true,
    "maxItems": 25
}

Example 2: narrow to a specific wedding month and year

{
    "firstName": "John",
    "lastName": "Smith",
    "eventMonth": "6",
    "eventYear": "2026",
    "includeVenue": true,
    "maxItems": 50
}

⚠️ Good to Know: The Knot requires both a first name and a last name to return results, one for each partner is fine. A name alone can match many couples, so use the month and year filters to narrow down. Venue, address, and ceremony or reception details appear only when the couple filled them in on their own public wedding website, so these fields are often blank. That is expected, not an error.

🔀 Two modes

The Actor runs in one of two modes, set by the mode input:

• Search mode (default): look up a name you already have. Provide firstName and lastName (optionally eventMonth / eventYear) and get back the matching public couples.
• Discover mode: for when you do not have a name yet. It browses The Knot's public couple directory and applies optional filters, usState and a weddingDateFrom / weddingDateTo range, with maxScan capping how many public IDs the run walks. It walks the newest public couple IDs downward, so the most recent and upcoming weddings come back first. onlyComplete pairs well with discover to drop sparse records. Like search mode, it reads only public pages.

{"mode":"discover","usState":"TX","maxScan":5000,"includeVenue":true,"maxItems":500}

📊 Output

Each record contains up to 22 fields. Schema:

🏷 Field	Key	Description
💑 Couple	coupleNames	Both partners joined, for example "Gregory Gion & Jessica Miller".
🎁 Registry URL	registryUrl	Public gift registry link.
🔗 Wedding Website	weddingWebsiteUrl	Public wedding-website URL (when the couple has one).
🆔 Couple ID	coupleId	The Knot's public couple identifier.
👤 Partner 1 First	partner1FirstName	First name of partner one.
👤 Partner 1 Last	partner1LastName	Last name of partner one.
👤 Partner 2 First	partner2FirstName	First name of partner two.
👤 Partner 2 Last	partner2LastName	Last name of partner two.
📅 Wedding Date	weddingDate	ISO wedding date (blank when the couple hid it).
🏙 City	city	Wedding city.
📍 State	state	Wedding state or province.
📮 ZIP	zip	Couple's ZIP / postal code when The Knot exposes it, otherwise null.
🌎 Country	country	Wedding country.
🗺 Location	location	Short location label from the search result.
🏛 Venue	venueName	Venue name (only when the couple added it).
📮 Venue Address	venueAddress	Full venue address (only when the couple added it).
🏙 Venue City	venueCity	Venue city.
📍 Venue State	venueState	Venue state.
💒 Ceremony	ceremonyVenue	Ceremony location.
🥂 Reception	receptionVenue	Reception location.
📌 Wedding Location Text	weddingLocationText	"City, ST" label from the wedding website.
💳 Cash Registry	hasTransactionalRegistry	Whether the couple has a cash / transactional registry.
🙈 Hidden Date	isHiddenDate	Whether the couple chose to hide their date.
🕒 Scraped At	scrapedAt	ISO timestamp of the scrape.

Real sample records

{
    "coupleNames": "Gregory Gion & Jessica Miller",
    "registryUrl": "https://registry.theknot.com/gregory-gion-jessica-miller-april-2025-fl/65174452",
    "weddingWebsiteUrl": "https://www.theknot.com/gregorygionandjessicamiller",
    "coupleId": "65174452",
    "partner1FirstName": "Gregory",
    "partner1LastName": "Gion",
    "partner2FirstName": "Jessica",
    "partner2LastName": "Miller",
    "weddingDate": "2025-04-05T00:00:00.000Z",
    "city": "DeLand",
    "state": "FL",
    "country": "USA",
    "location": "FL",
    "venueName": "Villa Festa",
    "venueAddress": "518 E. New York Ave., Deland, FL, 32720",
    "venueCity": "DeLand",
    "venueState": "FL",
    "ceremonyVenue": "Villa Festa",
    "receptionVenue": "Villa Festa",
    "weddingLocationText": "DeLand, FL",
    "hasTransactionalRegistry": false,
    "isHiddenDate": false,
    "scrapedAt": "2026-07-08T17:29:01.873Z"
}

{
    "coupleNames": "Jason Baczek & Jessica Miller",
    "registryUrl": "https://registry.theknot.com/jason-baczek-jessica-miller-september-2025-co/68709311",
    "weddingWebsiteUrl": "https://www.theknot.com/jasonbaczekandjessicamiller",
    "coupleId": "68709311",
    "partner1FirstName": "Jason",
    "partner1LastName": "Baczek",
    "partner2FirstName": "Jessica",
    "partner2LastName": "Miller",
    "weddingDate": "2025-09-13T00:00:00.000Z",
    "city": "Idaho Springs",
    "state": "CO",
    "country": "USA",
    "location": "CO",
    "venueName": "Blackstone Rivers Ranch",
    "venueAddress": "3673 Chicago Creek Rd., Idaho Springs, CO, 80452",
    "venueCity": "Idaho Springs",
    "venueState": "CO",
    "ceremonyVenue": "Blackstone Rivers Ranch",
    "receptionVenue": "Blackstone Rivers Ranch",
    "weddingLocationText": "Idaho Springs, CO",
    "hasTransactionalRegistry": true,
    "isHiddenDate": false,
    "scrapedAt": "2026-07-08T17:29:02.253Z"
}

{
    "coupleNames": "Shane Larocque & Jessica Miller",
    "registryUrl": "https://registry.theknot.com/shane-larocque-jessica-miller-october-2025-on/71755387",
    "weddingWebsiteUrl": "https://www.theknot.com/shanelarocqueandjessicamiller",
    "coupleId": "71755387",
    "partner1FirstName": "Shane",
    "partner1LastName": "Larocque",
    "partner2FirstName": "Jessica",
    "partner2LastName": "Miller",
    "weddingDate": "2025-10-03T00:00:00.000Z",
    "city": "Iroquois",
    "state": "ON",
    "country": "CA",
    "location": "ON",
    "venueName": null,
    "venueAddress": null,
    "venueCity": null,
    "venueState": null,
    "ceremonyVenue": null,
    "receptionVenue": null,
    "weddingLocationText": null,
    "hasTransactionalRegistry": false,
    "isHiddenDate": false,
    "scrapedAt": "2026-07-08T17:29:02.692Z"
}

The third record shows the honest reality: a real couple who published a wedding website and registry but did not add venue details, so those fields come back blank.

✨ Why choose this Actor

• Name in, structured profile out. No manual copy-paste from search pages.
• Both partners captured, not just the person you searched.
• Venue enrichment reads the couple's own public wedding-website page for venue, address, ceremony, and reception, when they provided them.
• Only public data. It reads what The Knot already displays publicly, nothing behind a login or passcode.
• Clean exports to CSV, Excel, JSON, and XML, ready for a CRM or spreadsheet.

📈 How it compares to alternatives

Approach	Both partners	Venue	Registry link	Structured export
Manual The Knot search	Partial	Manual	Manual	❌
Generic HTML scraper	❌	❌	❌	Partial
This Actor	✅	✅ (when public)	✅	✅

🚀 How to use

1. Sign up for a free Apify account using this link.
2. Open the Actor and enter a first name and last name.
3. (Optional) Add a wedding month and year to narrow results, and keep Include venue details on.
4. Click Start and wait for the run to finish.
5. Export your results as CSV, Excel, JSON, or XML from the dataset tab.

💼 Business use cases

🏛 Venue and vendor sales	📸 Photographers and planners
Confirm a lead's wedding date, city, and venue before sending a quote.	Verify event details a prospect gave you against their public page.

🎁 Registry and gifting	📊 Market research
Match a known couple to their public registry to send the right gift.	Structure public wedding details to study seasonality and locations.

🔌 Automating the Actor

Run it on a schedule or connect it to your stack with Apify integrations: Make, Zapier, Slack, Airbyte, GitHub, and Google Drive. Push new records straight into a spreadsheet, CRM, or database whenever a run finishes.

🌟 Beyond business use cases

• Research: study how wedding locations and seasons trend across public data.
• Personal: find a friend's public wedding website and registry from their name.
• Non-profit: structure publicly shared event details for community outreach.
• Experimentation: learn structured data extraction from a real public source.

🤖 Ask an AI assistant

Paste your exported data into ChatGPT, Claude, Perplexity, or Microsoft Copilot and ask it to summarize venues by region, group couples by month, or draft outreach notes.

❓ Frequently Asked Questions

1. What do I need to provide? A first name and a last name, both at least 2 characters. One name per partner is fine.

2. Can I use it without a name? Yes, with the optional discover mode. Set mode to discover and it browses The Knot's public couple directory with optional state and wedding-date filters, no name required. It still reads only public pages, and it does not sell or provide contact data. In the default search mode it works as an enrichment tool that resolves a first and last name you already have.

3. Why is the venue blank for some couples? Venue, address, and ceremony or reception details appear only when the couple added them to their own public wedding website. Many couples leave them blank.

4. Is any of this private or login-protected data? No. It reads only what The Knot already shows publicly on its open "Find a Couple" search and public wedding-website pages. Passcode-protected pages are skipped.

5. How many results can one name return? Common names can match dozens of couples. Use the month and year filters to narrow the set.

6. What date format is used? Wedding dates are ISO 8601 (for example 2025-09-13T00:00:00.000Z).

7. Does it work outside the US? Yes. Results include Canadian and other international couples when The Knot lists them.

8. What export formats are available? CSV, Excel, JSON, and XML.

9. Are both partners returned? Yes, both partners' first and last names are captured on every record.

10. How is the free plan limited? Free runs return up to 10 items. Paid plans support up to 1,000,000.

11. Can I schedule it? Yes, use Apify Schedules or any of the supported integrations.

12. Is the wedding date always present? Usually, but a couple can hide their date. When hidden, weddingDate is blank and isHiddenDate is true.

🔌 Integrate with any app

Every run produces a dataset you can pull via the Apify API or push through Make, Zapier, Slack, Airbyte, GitHub, and Google Drive into your own tools.

🔗 Recommended Actors

• Other lead and directory enrichment Actors by ParseForge
• Registry and gifting data Actors
• Local business and venue data Actors

💡 Pro Tip: browse the complete ParseForge collection.

🆘 Need Help? Open our contact form

⚠️ Disclaimer: This is an independent tool and is not affiliated with, endorsed by, or sponsored by The Knot or The Knot Worldwide. It collects only publicly available data that couples have chosen to publish on their public wedding websites and The Knot's public couple search. Use the data responsibly and in compliance with applicable laws, including privacy and anti-spam regulations. Do not use it to contact individuals who have not consented to be contacted.