# Shef API

> Shef home chef menus and dishes (unverified)

- Vendor: `shefapi` · version 1.0 · category Food · tags shef api, shef home chef api, homemade food api, shef menu api, shef dishes api, home cooked meals api
- Datasource: custom HTTP routes
- Marketplace page: https://apiclay.com/api/shefapi
- This document: https://apiclay.com/docs/shefapi.md
- OpenAPI 3.1: https://apiclay.com/api/shefapi/openapi.json
- MCP: connect https://api.apiclay.com/v1/mcp (see https://apiclay.com/llms.txt), then `apiclay_describe_api` with vendor `shefapi`
- Updated: 2026-11-18

## About

## Shef API

A Shef home chef's menu: the chef's profile and delivery prices plus the dishes they currently offer, with prices, descriptions and images.

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

### Routes

#### POST `/menus` - Menus (chef's dishes)
The chef and their dishes.

| Param | In | Type | Required | Description |
|---|---|---|---|---|
| variables.shefId | body (JSON) | string | yes | Chef slug from the chef's page URL `https://shef.com/order/shef/`, e.g. `issara-t`. |
| variables.zipCode | body (JSON) | string | no | Delivery zip code, e.g. `94704`. |

Returns (fields the source code reads; not yet verified live):
- `data.consumerFoodItems[]`: dishes with id, name, description, price, images and availability
- `data.shef`: chef profile and delivery prices

### Caveats

- These routes were written from MealMe's source code and have not been tested live yet (the site blocks plain requests from the test machine).
- The source site uses bot protection (requests without the site's per-browser x-bt tracker header are refused with 403); calls may be blocked until that is handled.
- Upstream calls change over time (embedded keys, field names). Verify responses before relying on them.
- Not affiliated with shef.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.

### POST /menus — Menus (chef's dishes)
- Gateway: `POST https://api.apiclay.com/v1/api/shefapi/menus`
- Body sample (JSON):

```json
{"variables": {"shefId": "issara-t", "zipCode": "94704"}}
```

- 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 POST "https://api.apiclay.com/v1/api/shefapi/menus" \
  -H "token: <YOUR_APICLAY_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"variables": {"shefId": "issara-t", "zipCode": "94704"}}'
```

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