# Cookpad Japan Recipe Scraper (`stone_jadex/cookpad-recipe-scraper`) Actor

Public Cookpad Japan (cookpad.com/jp) recipes: title, author nickname, ingredients with amounts and groups, numbered steps with photos, servings, tips, bookmark/like/cooksnap counts, category, dates. From public category and recipe pages. $1.50 per 1,000 recipes, no start fee. Respects robots.txt.

- **URL**: https://apify.com/stone_jadex/cookpad-recipe-scraper.md
- **Developed by:** [Stone Jade](https://apify.com/stone_jadex) (community)
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$1.50 / 1,000 recipes

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Cookpad Japan Recipe Scraper

Cookpad Japan Recipe Scraper gives food researchers and recipe dataset builders structured results from public pages. Start with Cookpad Japan category IDs or recipe URLs and export title, ingredients and amounts, steps, author and servings.

### What you can do

- Collect ingredient names and amounts alongside preparation steps to study recipe composition.
- Compare servings and ingredient counts across recipes in a chosen Japanese category.
- Keep author, category context and published engagement counts with recipes when available.

### Who uses it

- A food researcher can compare ingredients and portions across a category of Japanese side dishes.
- A meal-planning team can collect specific recipe URLs and review their ingredients and steps when preparing a recipe dataset.

### Result preview

**Illustrative only:** invented examples show the shape of the data; they are not real results. A dash indicates an unavailable value.

| Recipe | Servings | Ingredients | Steps | Category |
| --- | --- | --- | --- | --- |
| Example rice bowl | 2 | Rice; egg | 3 | Rice dishes |
| Example soup | 4 | Vegetables; stock | 4 | Soup |
| Example salad | 2 | Cucumber; dressing | 2 | Salad |

Fields may be absent when the source does not publish them.

### Why choose this Actor

- Category IDs follow Cookpad’s category ordering; direct recipe URLs let you choose individual recipes.
- Ingredient names and amounts are separated in the output, and steps are retained with recipe-level context.

### Pricing

Prices in **USD**, verified on 4 November 2026. Check the current Pricing tab before running.

| Result type | Event price |
| --- | ---: |
| Recipe | $1.5 per 1,000 results |

For example, 1,000 results at the recipe rate incur $1.5 in result-event charges. This calculation covers Actor event charges. Review Pricing for any separately listed platform usage; later access to stored data follows Apify's applicable storage pricing.

### Try it in three steps

1. Enter Cookpad Japan category IDs or recipe URLs. Set a small result limit for your first run.
2. Set a small maximum and, for category discovery, a page limit per category. Run the Actor.
3. Inspect the dataset and export the results in your preferred available format.

### Coverage and FAQ

**What are the limits?** Keyword search pages are not supported. Fields depend on what the public recipe publishes.

The requested result limit defaults to 50 and can be set up to 100,000 per run.

**Is this a live feed?** Each run is a snapshot of available source information. Recipes, ingredients, steps and published estimates may change after collection; a requested maximum is a ceiling, not a promise of that many results.

**Can I use the data for ongoing analysis?** Yes, export it to your own workflow. Scheduling repeated runs or acting on the exported results requires your own workflow.

# Changelog

This Actor's version history is a separate document: https://apify.com/stone_jadex/cookpad-recipe-scraper/changelog.md

# Actor input Schema

## `categories` (type: `array`):

Cookpad category ids or URLs, e.g. 177 or https://cookpad.com/jp/categories/1607. Recipes are read in the category's own order. Default 177 (今日のご飯・おかず). Keyword search pages are not supported (they are a JavaScript challenge page).

## `recipeUrls` (type: `array`):

Specific recipe pages, e.g. https://cookpad.com/jp/recipes/20394215. Read before categories. If you only give recipe URLs, no category is crawled.

## `maxItems` (type: `integer`):

Stop after this many recipes (you pay only for recipes delivered).

## `maxPagesPerCategory` (type: `integer`):

About 30 recipes per category page.

## `maxConcurrency` (type: `integer`):

Kept low on purpose to stay polite to Cookpad.

## `requestDelayMs` (type: `integer`):

Minimum gap between request starts. Never lower than 1000 ms.

## `maxRunSeconds` (type: `integer`):

Stops cleanly with a run-notice row when reached.

## Actor input object example

```json
{
  "categories": [
    "177"
  ],
  "maxItems": 50,
  "maxPagesPerCategory": 10,
  "maxConcurrency": 1,
  "requestDelayMs": 1500,
  "maxRunSeconds": 3000
}
```

# Actor output Schema

## `results` (type: `string`):

Recipe rows saved in the default dataset, followed by the optional free run-notice row when the run is truncated or finds nothing.

## `summary` (type: `string`):

Run counters, robots and HTTP statistics, errors and not-found URLs, unavailable-field notes, and the reason the run stopped.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "categories": [
        "177"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("stone_jadex/cookpad-recipe-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "categories": ["177"] }

# Run the Actor and wait for it to finish
run = client.actor("stone_jadex/cookpad-recipe-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "categories": [
    "177"
  ]
}' |
apify call stone_jadex/cookpad-recipe-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,stone_jadex/cookpad-recipe-scraper"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/MKeZXme5JgB6NLhe8/builds/o3c5jUe4fiChZNvZ7/openapi.json