# DoorDash API

> DoorDash store menus, item customizations and nested option lists

- Vendor: `doordashapi` · version 1.0 · category Food · tags doordash api, doordash menu api, doordash store api, food delivery api, restaurant menu api, doordash customizations api
- Datasource: custom HTTP routes
- Marketplace page: https://apiclay.com/api/doordashapi
- This document: https://apiclay.com/docs/doordashapi.md
- OpenAPI 3.1: https://apiclay.com/api/doordashapi/openapi.json
- MCP: connect https://api.apiclay.com/v1/mcp (see https://apiclay.com/llms.txt), then `apiclay_describe_api` with vendor `doordashapi`
- Updated: 2026-11-18

## About

## DoorDash API

Read a DoorDash store's menu (categories, items, prices) and an item's customization option lists from DoorDash's consumer app API, including nested option lists.

Data comes from **doordash.com** (https://www.doordash.com). Every route below calls the site's own endpoint directly and returns the upstream response unchanged.

Typical flow: `/menus` -&gt; `/customizations` -&gt; `/sub-customizations`

### Routes

#### GET `/menus` - Menus (store menu)
Returns the store's menu as display modules.

| Param | In | Type | Required | Description |
|---|---|---|---|---|
| store_id | path | string | yes | DoorDash store id (the number at the end of a doordash.com store link), e.g. `653630`. |
| lat | query | string | no | Customer latitude, e.g. `37.451061`. |
| lng | query | string | no | Customer longitude, e.g. `-122.181343`. |
| fulfillment_type | query | string | no | `Pickup` or `Delivery`. |

Returns (fields in the upstream response, as MealMe's parser reads them):
- `display_modules[]` with `type` `menu_book`: `data.current_menu_id` (active menu)
- `display_modules[]` with `type` `item_list`: one per category (`id` `category-`, `data.name`)
- `display_modules[].data.content[]`: items (`id`, `name`, `description`, `display_price`)

#### GET `/customizations` - Customizations (item options)
Returns one item's option lists.

| Param | In | Type | Required | Description |
|---|---|---|---|---|
| item_id | path | string | yes | Item `id` from `/menus`. |
| store_id | query | string | yes | Store id, e.g. `653630`. |

Returns (fields in the upstream response, as MealMe's parser reads them):
- `display_modules[]` with `type` `option_list`: option groups (`data.id`, `data.name`, `data.subtitle`, `data.selection_mode`, `data.min_num_options`, `data.max_num_options`)
- `display_modules[].data.content[]`: options (`id`, `name`, `price.unit_amount` in cents, `next_cursor.cursor` when the option has nested choices)

#### GET `/sub-customizations` - Sub customizations (nested options)
Returns the nested option lists behind one option.

| Param | In | Type | Required | Description |
|---|---|---|---|---|
| cursor | path | string | yes | An option's `next_cursor.cursor` from `/customizations`. |
| store_id | query | string | yes | Store id, e.g. `653630`. |

Returns (fields in the upstream response, as MealMe's parser reads them):
- `display_modules[]` with `type` `option_list`: option groups (`data.id`, `data.name`, `data.subtitle`, `data.selection_mode`, `data.min_num_options`, `data.max_num_options`)
- `display_modules[].data.content[]`: options (`id`, `name`, `price.unit_amount` in cents, `next_cursor.cursor` when the option has nested choices)

### Caveats

- The source site uses bot protection (Cloudflare); calls may be blocked until that is handled.
- These routes were written from MealMe's integration code and have not yet returned live data through this listing.
- DoorDash's app API expects the token of a signed-in DoorDash account. This listing uses no account and sends no token, so calls may be refused (401/403) until that is solved.
- Upstream calls change over time (embedded keys, field names). Verify responses before relying on them.
- Not affiliated with doordash.com.

## Pricing

- Pay as you go: 0.0012 credits/request
- Trial: 1 free requests per buyer
- Billing order: trial requests -> subscribed plan requests -> pay as you go. 1 credit's USD value is shown on the marketplace page.

## HTTP routes

Only the public, buyer-facing parts of each route are listed; vendor-side credentials stay on the gateway.

### GET /menus — Menus (store menu)
- Gateway: `GET https://api.apiclay.com/v1/api/doordashapi/menus`
- Public query params: `lng` (string), `lat` (string), `fulfillment_type` (string), `store_id` (string, required)
- Upstream proxy: ApiClay proxy paid by the vendor (data cap 2 MB per call). Fetched through an ApiClay proxy paid by the vendor; a response larger than the route's data cap fails with 502 and is refunded in full.

### GET /customizations — Customizations (item options)
- Gateway: `GET https://api.apiclay.com/v1/api/doordashapi/customizations`
- Public query params: `store_id` (string, required), `item_id` (string, required)
- Upstream proxy: ApiClay proxy paid by the vendor (data cap 2 MB per call). Fetched through an ApiClay proxy paid by the vendor; a response larger than the route's data cap fails with 502 and is refunded in full.

### GET /sub-customizations — Sub customizations (nested options)
- Gateway: `GET https://api.apiclay.com/v1/api/doordashapi/sub-customizations`
- Public query params: `store_id` (string, required), `cursor` (string, required)
- Upstream proxy: ApiClay proxy paid by the vendor (data cap 2 MB per call). Fetched through an ApiClay proxy paid by the vendor; a response larger than the route's data cap fails with 502 and is refunded in full.

## Call example

```bash
curl -X GET "https://api.apiclay.com/v1/api/doordashapi/menus?store_id=<store_id>" \
  -H "token: <YOUR_APICLAY_TOKEN>"
```

Index of every published API: https://apiclay.com/llms.txt
