# Favor Delivery API

> Favor Delivery merchant menus with items, sizes and option groups

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

## About

## Favor API

Read a Favor Delivery merchant's menus: sections, items, prices in cents, sizes and option groups.

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

### Routes

#### GET `/menus` - Menus (merchant menus)
Returns the merchant's menus with items, sizes and option groups.

| Param | In | Type | Required | Description |
|---|---|---|---|---|
| merchant_id | path | string | yes | Favor merchant id, the number at the end of a favordelivery.com merchant link, e.g. `28855`. |

Returns (fields in the upstream response, as MealMe's parser reads them):
- `menu.sections[]` (or `menu[]`): menu sections with `name`
- `...menu_items[]`: items (`id`, `name`, `display_name`, `description`, `instructions_default_text`, `price` in cents, `text_box`)
- `...menu_items[].sizes[]`: sizes (`id`, `size_text`, `absolute_price`)
- `...menu_items[].option_groups[]`: option groups (`id`, `name`, `required_description`, `min_selectable`, `max_selectable`, `options[]` with `id`, `name`, `price`, `availability`)

### Caveats

- The source site uses bot protection (not identified; MealMe sends these calls through a browser-spoofing service and residential proxies); 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 API needs an anonymous guest token. The gateway first opens a favordelivery.com page 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 favordelivery.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 (merchant menus)
- Gateway: `GET https://api.apiclay.com/v1/api/favordeliveryapi/menus`
- Public query params: `merchant_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/favordeliveryapi/menus?merchant_id=<merchant_id>" \
  -H "token: <YOUR_APICLAY_TOKEN>"
```

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