Epicurious Recipes Scraper
Pricing
from $19.00 / 1,000 results
Epicurious Recipes Scraper
Scrapes Epicurious recipes by search query. Returns each recipe as a flat row with ingredients, instructions, and metadata.
Pricing
from $19.00 / 1,000 results
Rating
0.0
(0)
Developer
ParseForge
Maintained by CommunityActor stats
0
Bookmarked
3
Total users
1
Monthly active users
2 days ago
Last modified
Categories
Share
Epicurious Recipes Scraper
Scrape Epicurious recipes by ingredient or dish, up to a million per run. Every recipe comes with its ingredients, instructions, and metadata. No login or API key. Export to CSV, JSON, Excel, or XML.
Epicurious recipes are locked behind a website built for browsing, not for bulk analysis. This actor searches the public recipe pages directly, so you can collect thousands of recipes by keyword without writing a scraper or dealing with rate limits. It returns each recipe as one flat row, ready for your food database, meal planner, or research project.
| Who uses it | What they scrape Epicurious for |
|---|---|
| Food bloggers | Build a reference library of recipes for a specific ingredient or cuisine |
| Meal planning apps | Populate a database of recipes with structured ingredients and steps |
| Nutrition researchers | Collect a large sample of recipes to analyze ingredient patterns |
| Recipe aggregators | Gather recipes from Epicurious to feature alongside other sources |
What it does
This Actor searches Epicurious for recipes matching a keyword and returns each recipe as a flat row with its ingredients, instructions, and metadata.
- π Keyword search: Enter any ingredient or dish, like 'pasta' or 'chocolate cake', and get matching recipes.
- π Structured output: Each recipe is returned as a flat row with ingredients, instructions, and metadata, ready for CSV or JSON.
- β‘ Scalable collection: Set a maximum number of recipes up to 1,000,000 per run.
- π‘οΈ No login required: The actor reads public pages, so you don't need an Epicurious account or API key.
Results export to CSV, JSON, Excel, or XML, or straight from the API.
What you can do with Epicurious data
π Build a recipe database.
A meal planning startup runs the actor with 'pasta' and collects 10,000 recipes to seed their app's search index.
π Analyze ingredient trends.
A food researcher scrapes recipes for 'plant-based' over several months to track how ingredient lists change.
π Create a niche cookbook.
A food blogger searches for 'summer desserts' and uses the structured ingredients to curate a themed recipe collection.
π§ͺ Test recipe variations.
A chef collects all recipes for 'chocolate chip cookies' to compare ratios and techniques before developing their own.
Why choose this scraper
| What you get | |
|---|---|
| Search by keyword | Find recipes for any ingredient or dish, from 'vegan dinner' to 'gluten-free bread'. |
| Flat row per recipe | Each recipe is returned as one record with all its data, no nested JSON to parse. |
| Up to 1M recipes | Collect a large dataset in a single run, limited only by what Epicurious returns. |
| Export anywhere | Download as CSV, JSON, Excel, or XML, or push to a dataset for further processing. |
How it compares
This actor focuses on keyword search for Epicurious recipes, while competitors may offer broader site coverage or URL-based scraping.
| Feature | ParseForge | Recipe Data Scraper - Extract from 500+ Cooking Websites | Epicurious Recipes Scraper | Epicurious Recipe Scraper |
|---|---|---|---|---|
| Scrapes Epicurious specifically | Yes | Yes | Yes | Yes |
| Keyword search | Yes | Not listed | Not listed | Yes |
| Scrapes 500+ other cooking websites | No | Yes | No | No |
| URL-based scraping | No | Not listed | Not listed | Yes |
| Returns ingredients and instructions | Yes | Yes | Yes | Yes |
| Returns nutrition facts | Not listed | Yes | Not listed | Not listed |
| Filter by cuisine or diet | No | Not listed | Not listed | Yes |
Configure the run
Drive the Actor with a single search query, and set a maximum number of recipes to collect per run. The Input tab lists every parameter.
A first run with the defaults:
{"searchQuery": "pasta","maxItems": 10}
A larger pull:
{"searchQuery": "pasta","maxItems": 200}
Pricing
Pay-per-result: $0.021 per result collected. You pay only for the results written to your dataset.
| Results collected | Approximate cost |
|---|---|
| 100 results | $2.10 |
| 1,000 results | $21.00 |
| 10,000 results | $210.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
- Create a free Apify account with $5 in credit.
- Open the Epicurious Recipes Scraper.
- Set your inputs and any filters, then click Start.
- 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 Epicurious 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/epicurious-scraper"
Then prompt it in plain language to run the scraper and read back the results.
Troubleshooting
Why am I getting no results?
Your search query may be too specific or misspelled. Try a broader term like 'pasta' instead of 'gluten-free pasta with sun-dried tomatoes'. Also check that Epicurious is accessible from your location.
The actor returns fewer recipes than my maxItems setting.
Epicurious may not have that many results for your query. The actor stops when it has collected all available recipes or reaches the maximum, whichever comes first.
I'm getting blocked or seeing errors.
Epicurious may be rate-limiting your requests. Reduce the frequency of your runs or add a longer delay between requests. Using Apify's residential proxies can also help avoid blocks.
Some recipe fields are empty.
Not all recipes on Epicurious have the same metadata. Fields like ratings or cook time may be missing for some recipes. The actor returns whatever is available on the page.
FAQ
| Question | Answer |
|---|---|
| What does this actor scrape from Epicurious? | It scrapes recipe pages found through the search query. Each result includes the recipe title, ingredients, instructions, and metadata like ratings, cook time, and servings, depending on what is available on the page. |
| Do I need an Epicurious account or API key? | No. The actor reads the public website, so no login or API key is required. |
| How many recipes can I get in one run? | You can set the maximum number of recipes up to 1,000,000. The actual number returned depends on how many results Epicurious returns for your query. |
| Can I scrape a specific recipe by URL? | This actor is designed for keyword search. To scrape a specific URL, you would need a different actor or a custom scraper. |
| What format is the data returned in? | The actor returns data as a flat JSON object per recipe. You can export the dataset to CSV, JSON, Excel, or XML from the Apify platform. |
| Is this actor legal to use? | You are responsible for complying with Epicurious's terms of service and any applicable laws. Always review the website's robots.txt and terms before scraping at scale. |
| Can I filter recipes by cuisine or diet? | The current input only supports a free-text search query. You can include terms like 'vegan' or 'Italian' in your query to narrow results, but there are no separate filter fields. |
| How often is the data updated? | The actor scrapes live data from Epicurious each time you run it, so you get the current state of the website. |
| What if my search returns no results? | Check your query for typos or try a broader term. Epicurious may also block automated requests if you run too frequently, so consider adding delays between runs. |
| Can I run this actor on a schedule? | Yes, you can schedule runs in the Apify console to collect new recipes periodically. |
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 CondΓ© Nast. 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.
