# McDonalds API

> McDonald's store product catalog with prices, menu categories and store menu hours

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

## About

## McDonald's API

Read a McDonald's restaurant's product catalog with prices and recipe choices, the US menu category list, and the restaurant's details (menu day parts, unavailable products) from the McDonald's app API.

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

Typical flow: `/store` -&gt; `/menus` + `/categories`

### Routes

#### GET `/menus` - Menus (store product catalog)
Returns the store's product catalog with prices and recipe choices.

| Param | In | Type | Required | Description |
|---|---|---|---|---|
| store_id | path | string | yes | McDonald's national store number (the number at the end of a mcdonalds.com location link), e.g. `4861`. |

Returns (fields in the upstream response, as MealMe's parser reads them):
- `Store[0].Products[]`: products (`ProductCode`, `Names`, `ProductType`, `MenuTypeID`, `ExtendedMenuTypeID`, `Categories[].DisplayCategoryID`, `DisplayImageName`, `Recipe` with choices and ingredients: `ProductCode`, `MinQuantity`, `MaxQuantity`, `DefaultQuantity`, `ChargeTreshold`)
- `Store[0].ProductPrice[]`: prices per `ProductCode` (`Prices[].Price`, `IsValid`)
- `status.errors[]`: e.g. `No Catalog Data Found for given request` for an inactive store

#### GET `/categories` - Categories (US menu categories)
Returns the US menu category tree (shared by all stores).

Returns (fields in the upstream response, as MealMe's parser reads them):
- `response.categories[]`: categories (`id`, `parentId`, `menuTypeId`, `names` with `locale` / `longname`, `displayOrder`); products point to them through `DisplayCategoryID` in `/menus`

#### GET `/store` - Store (restaurant details)
Returns the restaurant's details, menu day parts and product availability.

| Param | In | Type | Required | Description |
|---|---|---|---|---|
| store_id | path | string | yes | National store number, e.g. `4861`. |

Returns (fields in the upstream response, as MealMe's parser reads them):
- `response.restaurant.order.storeMenuTypeCalendar[]`: menu day parts (`menuTypeID`, `weekDay`, `startTime`, `endTime`)
- `response.restaurant.availableMenuProducts.[]`: products sold in each menu type
- `response.restaurant.catalog.outageProductCodes[]`: products currently unavailable
- `response.restaurant.location.latitude`, `.longitude`: location

### Caveats

- The source site uses bot protection (Akamai Bot Manager); 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.
- The app API needs a guest bearer token. The gateway first opens mcdonalds.com as a guest and reuses the token that page sends; you do not send any token.
- Upstream calls change over time (embedded keys, field names). Verify responses before relying on them.
- Not affiliated with mcdonalds.com.

## Pricing

- Pay as you go: 0.01 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 product catalog)
- Gateway: `GET https://api.apiclay.com/v1/api/mcdonaldsapi/menus`
- Public query params: `store_id` (string, required)
- Upstream proxy: ApiClay proxy paid by the vendor (data cap 10 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 /categories — Categories (US menu categories)
- Gateway: `GET https://api.apiclay.com/v1/api/mcdonaldsapi/categories`
- Upstream proxy: ApiClay proxy paid by the vendor (data cap 10 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 /store — Store (restaurant details)
- Gateway: `GET https://api.apiclay.com/v1/api/mcdonaldsapi/store`
- Public query params: `store_id` (string, required)
- Upstream proxy: ApiClay proxy paid by the vendor (data cap 10 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/mcdonaldsapi/menus?store_id=<store_id>" \
  -H "token: <YOUR_APICLAY_TOKEN>"
```

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