# Hot Pepper Gourmet Japan Restaurant Scraper (`stone_jadex/hotpepper-gourmet-japan-restaurant-scraper`) Actor

Public Hot Pepper Gourmet (ホットペッパーグルメ) restaurants: shop id, name, genre, budget, station, phone, coupons. Optional detail page. No start fee. Draft PPE only.

- **URL**: https://apify.com/stone_jadex/hotpepper-gourmet-japan-restaurant-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

Pay per event

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

## Hot Pepper Gourmet Japan Restaurant Scraper

Hot Pepper Gourmet Japan Restaurant Scraper gives restaurant researchers and travel data teams structured results from public pages. Start with a prefecture with optional genre or area, or a list or shop URL and export restaurant name, genre, station, budgets and public contact information.

### What you can do

- Compare restaurants by genre, nearest station and published lunch or dinner budget.
- Use area and access information to build a geographically relevant dining shortlist.
- Examine published hours, seating and parking in detail mode when planning a deeper venue review.

### Who uses it

- A travel product team can collect restaurants near a Tokyo sub-area and present genres and budget information.
- A restaurant researcher can compare nearby venues by access and seating, checking detail pages for operating information.

### Result preview

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

| Restaurant | Genre | Station | Lunch budget | Dinner budget |
| --- | --- | --- | --- | --- |
| Example dining room | Japanese | Example station | 1,000 JPY | 3,000 JPY |
| Example café | Cafe | Example station | 1,200 JPY | 2,000 JPY |
| Example kitchen | Italian | Example station | — | 4,000 JPY |

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

### Why choose this Actor

- Choose a prefecture and optional genre or sub-area, or provide a specific shop URL.
- List rows provide station, budget and genre context; optional detail enrichment adds address, hours, seats, parking and ratings when available.

### Pricing

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

| Result type | Event price |
| --- | ---: |
| List restaurant | $1.5 per 1,000 results |
| Restaurant with details | $1.5 per 1,000 results |

The detail event replaces the list event for the same result; the two are not added together. For example, 1,000 results at the list restaurant 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 a prefecture with optional genre or area, or a list or shop URL. Set a small result limit for your first run.
2. Turn on **Open each shop page** for addresses, hours and other shop-page information, or leave it off for list results. Run the Actor.
3. Inspect the dataset and export the results in your preferred available format.

### Coverage and FAQ

**What are the limits?** List rows do not include all detail-page fields. Restaurant information can be missing or change.

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

**Is this a live feed?** Each run is a snapshot of available source information. Restaurant information and budgets 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/hotpepper-gourmet-japan-restaurant-scraper/changelog.md

# Actor input Schema

## `prefecture` (type: `string`):

Hot Pepper service-area code (SA##) or Japanese name. Default SA11 (東京).

## `genre` (type: `string`):

Optional Hot Pepper genre code (G001–G017).

## `subArea` (type: `string`):

Optional Hot Pepper area code such as Y005 (銀座・新橋) or X020. Combined with prefecture/genre in the list URL.

## `startUrls` (type: `array`):

Optional. A list URL such as https://www.hotpepper.jp/SA11/bgn1/ or a shop URL such as https://www.hotpepper.jp/strJ003763598/. Empty input uses prefecture/genre/subArea (default 東京).

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

Stop after this many charged shop rows. Alias: maxResults.

## `maxResults` (type: `integer`):

Alias for maxItems.

## `maxPages` (type: `integer`):

Optional. Each list page has about 22 shops.

## `includeDetails` (type: `boolean`):

Adds address, hours, seats, parking, rating, and other detail-table fields. Charged as shop-detail instead of shop.

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

At least one second between request starts. A Crawl-delay in robots.txt can only raise this.

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

How many list or shop pages may be requested at once. Default 1 (serial). Starts are still spaced by requestDelayMs.

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

Stops cleanly and writes the OUTPUT record before this limit.

## `proxyConfiguration` (type: `object`):

Direct connection by default (opt-in). Residential is a fallback only.

## `useProxyFallback` (type: `boolean`):

Stay on a direct connection until repeated HTTP 403 or 429, then switch to the configured proxy.

## `allowDetailOnResidential` (type: `boolean`):

Shop detail pages stay on a direct connection when the proxy group is residential, unless this is on. Residential download budget is a fixed developer cap (5 MB), not user-tunable.

## Actor input object example

```json
{
  "prefecture": "SA11",
  "maxItems": 50,
  "includeDetails": false,
  "requestDelayMs": 1000,
  "maxConcurrency": 1,
  "maxRunSeconds": 3600,
  "proxyConfiguration": {
    "useApifyProxy": false
  },
  "useProxyFallback": false,
  "allowDetailOnResidential": false
}
```

# Actor output Schema

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

Shop rows saved in the default dataset. Detail fields are present only when includeDetails fetched a shop page; a truncated run also appends one run-notice row.

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

Counts, stop reason, HTTP and robots statistics, pricing, the run input and unavailable-field notes written to the OUTPUT key-value record.

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("stone_jadex/hotpepper-gourmet-japan-restaurant-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 = {}

# Run the Actor and wait for it to finish
run = client.actor("stone_jadex/hotpepper-gourmet-japan-restaurant-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 '{}' |
apify call stone_jadex/hotpepper-gourmet-japan-restaurant-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,stone_jadex/hotpepper-gourmet-japan-restaurant-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/IuDs6IIIhcOgSWLn3/builds/tAm3ueP98nYDfvzhZ/openapi.json