# DoorDash Storefront API

> DoorDash Storefront (order.online) store menus and item option lists

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

## About

## DoorDash Storefront API

DoorDash Storefront powers restaurants' own ordering sites on order.online. Read a store's menu (categories, items, prices, images) from its store page, and an item's option lists, including nested options, from the item page API.

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

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

### Routes

#### GET `/menus` - Menus (store page)
Returns the store page HTML; the menu is the JSON in `

## 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 page)
- Gateway: `GET https://api.apiclay.com/v1/api/doordashstorefrontapi/menus`
- Public query params: `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.

### POST /customizations — Customizations (item option lists)
- Gateway: `POST https://api.apiclay.com/v1/api/doordashstorefrontapi/customizations`
- Body sample (JSON):

```json
{"variables": {"itemId": "<item id from /menus>", "consumerId": null, "storeId": "653630", "isMerchantPreview": false, "isNested": false, "shouldFetchPresetCarousels": true, "fulfillmentType": "Pickup", "cursorContext": {"itemCursor": "<item nextCursor from /menus>"}, "shouldFetchStoreLiteData": false}}
```

- 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/doordashstorefrontapi/menus?store_id=<store_id>" \
  -H "token: <YOUR_APICLAY_TOKEN>"
```

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