Bon Appétit Recipes Scraper
Pricing
from $3.00 / 1,000 recipe records
Bon Appétit Recipes Scraper
Scrape public Bon Appétit recipe pages and recipe indexes into structured records with ingredients, instructions, timing, author, yield, keywords, and optional nutrition.
Pricing
from $3.00 / 1,000 recipe records
Rating
0.0
(0)
Developer
Muhammad Afzal
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
4 days ago
Last modified
Categories
Share
Scrapes public Bon Appétit recipe pages and returns normalized recipe records for recipe databases, meal-planning workflows, food research, and AI agents.
Use startUrls for public recipe or index pages, or searchQuery to discover recipes by keyword. maxResults defaults to 10 (1–100), maxPages defaults to 3 (1–10), and includeNutrition keeps nutrition data from Recipe JSON-LD when available. With no input, the Actor uses Bon Appétit’s public recipes index.
Each dataset item includes the recipe URL, name, description, image, author, publication date, prep/cook/total times, yield, categories, cuisine, keywords, ingredients, instructions, nutrition, scrape timestamp, and extraction warnings. The Actor returns only schema-valid recipe records; blocked or empty runs return zero fabricated records and explain the outcome in OUTPUT and the terminal status.
Example:
{"startUrls": [{ "url": "https://www.bonappetit.com/bon-appetit/recipe/one-pot-ratatouille" }],"maxResults": 1,"includeNutrition": true}
Bon Appétit content remains subject to the source website’s terms and robots/access policies. This Actor accesses public pages only and does not bypass authentication, paywalls, CAPTCHAs, or other access controls.
What data does Bon Appétit Recipes Scraper return?
| Field | Type | Description |
|---|---|---|
recordType | string | Record Type |
url | string | Recipe URL |
recipeId | string or null | Recipe ID |
name | string | Recipe Name |
description | string or null | Description |
image | string or null | Image URL |
author | string or null | Author |
datePublished | string or null | Value returned as datePublished. |
prepTime | string or null | Value returned as prepTime. |
cookTime | string or null | Value returned as cookTime. |
totalTime | string or null | Value returned as totalTime. |
recipeYield | string or null | Value returned as recipeYield. |
recipeCategory | array | Value returned as recipeCategory. |
recipeCuisine | array | Value returned as recipeCuisine. |
keywords | array | Value returned as keywords. |
ingredients | array | Value returned as ingredients. |
instructions | array | Value returned as instructions. |
nutrition | object or null | Value returned as nutrition. |
scrapedAt | string | Value returned as scrapedAt. |
warnings | array | Value returned as warnings. |
Use cases
- Schedule repeatable collection and export results to downstream workflows.
- Run a one-off research job and export the structured result as JSON, CSV, Excel, XML, or RSS from Apify.
- Schedule the same input to monitor changes over time and send completed datasets to a webhook or integration.
- Feed schema-shaped records into a database, spreadsheet, BI tool, or AI workflow with the source URL retained for verification.
Input
| Field | Type | Description |
|---|---|---|
startUrls | array | Use for public Bon Appétit recipe, category, or search pages. Example: https://www.bonappetit.com/bon-appetit/recipe/one-pot-ratatouille. |
searchQuery | string | Use to discover Bon Appétit recipes by keyword, for example 'chicken pasta'. Leave empty when using startUrls. |
maxResults | integer | Maximum structured recipe records to return; 1-100. Each valid recipe is one result event. |
maxPages | integer | Maximum index/search pages for recipe-link discovery; 1-10. Direct recipe URLs do not use this limit. |
includeNutrition | boolean | Keep nutrition fields from Recipe JSON-LD when available. |
Output example
{"recordType": "Example Record Type","url": "Example Recipe URL","recipeId": "Example Recipe ID","name": "Example Recipe Name","description": "Example Description","image": "Example Image URL","author": "Example Author","datePublished": "Example datePublished","prepTime": "Example prepTime","cookTime": "Example cookTime","totalTime": "Example totalTime","recipeYield": "Example recipeYield"}
The exact fields depend on the selected input and what the public source exposes. Use the dataset schema as the machine-readable contract and retain source URLs for verification.
Run Bon Appétit Recipes Scraper with the Apify API
import { ApifyClient } from 'apify-client';const client = new ApifyClient({ token: process.env.APIFY_TOKEN });const run = await client.actor('muhammadafzal/bon-appetit-recipes-scraper').call({"startUrls": [],"searchQuery": "","maxResults": 10,"maxPages": 3,"includeNutrition": true});const { items } = await client.dataset(run.defaultDatasetId).listItems();console.log(items);
You can also run the Actor from Apify Console, schedules, webhooks, the REST API, Make, Zapier, n8n, or the hosted Apify MCP server.
Pricing and cost control
This Actor uses pay-per-event pricing. Charges follow the live event definitions shown below.
| Event | Price (USD) | When it is charged |
|---|---|---|
recipe-record | $0.003 | Charged once for each schema-valid Bon Appétit recipe record returned. |
apify-actor-start | $0.00005 | Charged when the Actor starts running. Number of events charged depends on Actor memory (one event per GB, minimum one event). |
For example, 100 recipe-record events cost $0.3, plus any enabled Actor-start event. Empty or failed work should be checked in the run log and dataset before reuse.
Responsible use
Use this Actor only for data you are authorized to access. Follow the target website's terms, robots and access policies, and applicable privacy, database, copyright, anti-spam, and data-protection laws. Do not use it to bypass authentication or other access controls, collect private data, harass people, or make high-impact decisions without independent verification.
Support
When reporting a problem, include the Actor run ID, a redacted input, the expected result, and a small public example URL when applicable. Do not post API tokens, cookies, credentials, or personal data in an issue.