# DoorDash Store Menu & FAQ Data Finder (`nimbryxo-studio/doordash-store-menu-and-faq-data-finder`) Actor

Find DoorDash restaurant store details and complete menus by store URL, including name, address, cuisine breadcrumbs, menu sections with item names, descriptions, and prices, and the store's published FAQ.

- **URL**: https://apify.com/nimbryxo-studio/doordash-store-menu-and-faq-data-finder.md
- **Developed by:** [Nimbryxo-studio](https://apify.com/nimbryxo-studio) (community)
- **Categories:** E-commerce, Automation, Lead generation
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.49 / 1,000 results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## DoorDash Store Menu & FAQ Data Finder

Find restaurant details and complete menus from **DoorDash** store pages — name, address, cuisine breadcrumbs, menu sections with item names, descriptions and prices, and the store's published FAQ. Provide one or more store URLs and get a flat, fully-populated record back for each.

### What this actor does

- **Full menu extraction** — every section and item, with name, description, and price
- **FAQ extraction** — questions and answers published on the restaurant's store page
- **Breadcrumb extraction** — cuisine type and neighborhood, as shown on the page
- **Deduplication** — the same store ID is only emitted once per run, even if its URL is listed twice
- **Always-populated fields** — every field is present with a typed default (empty string, `0`, or `[]`) rather than `null`, so downstream code never needs to check for missing keys

### Output per restaurant

- `storeId` — DoorDash store ID (from the URL)
- `storeName`, `storeUrl`
- `title`, `description` — the page's title and meta description
- `address`, `city`, `state`
- `breadcrumbs[]` — page breadcrumb trail, e.g. `["Home", "Boston", "Burgers", "UBURGER"]` (last is the restaurant name, second-to-last is typically the cuisine)
- `menuSections[]` — section names, e.g. `["Salads", "Burgers", "Drinks"]`
- `menuSectionCount`
- `menuItems[]` — flat list of `{section, name, description, price}`
- `menuItemCount`
- `faq[]` — list of `{question, answer}` pairs
- `faqCount`
- `scrapedAt`

### Input

| Field | Type | Default | Description |
|---|---|---|---|
| `storeUrls` | array | – | DoorDash store URLs to scrape |
| `maxItems` | integer | `10` | Maximum restaurants to scrape across all URLs (1–100) |

#### Example: scrape a list of specific stores

```json
{
  "storeUrls": [
    "https://www.doordash.com/store/15034",
    "https://www.doordash.com/store/6422"
  ],
  "maxItems": 10
}
```

#### Example: a single store

```json
{
  "storeUrls": ["https://www.doordash.com/store/15034"],
  "maxItems": 1
}
```

### Use cases

- **Competitor menu intelligence** — track pricing and item offerings for named restaurants over time
- **Cuisine analysis** — group restaurants by their breadcrumb cuisine tag
- **Menu engineering research** — compare which sections and items are common across similar restaurants
- **Franchise auditing** — pull menus for every location of a chain by store URL
- **Customer support/FAQ research** — collect how restaurants answer common ordering questions

### FAQ

**Why doesn't this return individual customer reviews?** DoorDash store pages no longer expose individual customer reviews — only aggregate signals surfaced elsewhere on the page. This actor extracts everything the store page actually publishes: menu, address, FAQ, and breadcrumbs.

**How do I find a store's URL?** Visit the restaurant on doordash.com and copy its page URL, in the form `https://www.doordash.com/store/<id>`.

**Can I get prices as numbers instead of strings?** Prices are returned as strings (e.g. `"$8.50"`) because DoorDash sometimes shows ranges or non-numeric formatting. Convert them downstream if you need numeric values.

**Will this work for every DoorDash store?** It works for any restaurant with a published menu. Some stores — closed restaurants, catering/aggregator brands, or convenience-store and grocery listings — don't expose a structured menu; for those, this actor still returns the restaurant's info, FAQ, breadcrumbs, and address, but `menuSections` and `menuItems` come back empty.

**Does this include duplicate stores if I list the same URL twice?** No — each store ID is only emitted once per run even if its URL appears more than once in `storeUrls`.

**Is this affiliated with DoorDash?** No. This is an independent third-party actor that reads DoorDash's public store pages.

# Actor input Schema

## `storeUrls` (type: `array`):

DoorDash store URLs (e.g., https://www.doordash.com/store/15034). Each store will be scraped for full menu + restaurant info.

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

Maximum number of restaurants to scrape across all URLs.

## Actor input object example

```json
{
  "storeUrls": [
    "https://www.doordash.com/store/15034"
  ],
  "maxItems": 1
}
```

# Actor output Schema

## `reviews` (type: `string`):

No description

# 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 = {
    "storeUrls": [
        "https://www.doordash.com/store/15034"
    ],
    "maxItems": 1
};

// Run the Actor and wait for it to finish
const run = await client.actor("nimbryxo-studio/doordash-store-menu-and-faq-data-finder").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 = {
    "storeUrls": ["https://www.doordash.com/store/15034"],
    "maxItems": 1,
}

# Run the Actor and wait for it to finish
run = client.actor("nimbryxo-studio/doordash-store-menu-and-faq-data-finder").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 '{
  "storeUrls": [
    "https://www.doordash.com/store/15034"
  ],
  "maxItems": 1
}' |
apify call nimbryxo-studio/doordash-store-menu-and-faq-data-finder --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,nimbryxo-studio/doordash-store-menu-and-faq-data-finder"
        }
    }
}
```

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/YQuuDIpkXOu0xEPQ1/builds/hLiM39f0cZYa0ohpd/openapi.json