# TouchBistro API

> TouchBistro online ordering menus with items and modifier groups

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

## About

## TouchBistro API

Read the online-ordering menu of a restaurant on TouchBistro (order.tbdine.com): menu pages, groups, items with prices and images, and modifier groups with their options.

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

Typical flow: `/menu-page` -&gt; `/menus`

The venue id is the number in a TouchBistro ordering URL: `order.tbdine.com/delivery/42671/menu` -&gt; `42671`.

`/menus` reads TouchBistro's Next.js data file, whose path contains a build id that changes every time TouchBistro deploys. Read the current `buildId` from the `__NEXT_DATA__` script in `/menu-page` and pass it as `build_id`.

### Routes

#### GET `/menu-page` - Menu page (ordering page HTML)
Returns the venue's ordering page as HTML. Its `__NEXT_DATA__` script holds `buildId`.

| Param | In | Type | Required | Description |
|---|---|---|---|---|
| fulfillment | path | string | yes | `delivery` or `pickup`. |
| venue_id | path | string | yes | Venue id, e.g. `42671`. |
| orderMethod | query | string | yes | Same as `fulfillment`. |
| venueXRefID | query | string | yes | Same as `venue_id`. |

Returns: HTML with `__NEXT_DATA__` (`buildId` for `/menus`).

#### GET `/menus` - Menus (operational menu of a venue)
Returns the venue's menu as JSON.

| Param | In | Type | Required | Description |
|---|---|---|---|---|
| build_id | path | string | yes | Current Next.js build id, `buildId` from `/menu-page`. Changes on every TouchBistro deploy. |
| fulfillment | path | string | yes | `delivery` or `pickup`. |
| venue_id | path | string | yes | Venue id, e.g. `42671`. |
| orderMethod | query | string | yes | Same as `fulfillment`. |
| venueXRefID | query | string | yes | Same as `venue_id`. |

Returns (fields read by the source code; not yet verified live):
- `pageProps.operationalMenu.menuPages[]`, `.menuGroups..label`, `.menuItemRefs[]`: menu pages and groups
- `pageProps.operationalMenu.menuItems..label`, `.description`, `.price`, `.image`, `.isOutOfStock`: item
- `pageProps.operationalMenu.menuItems..modifierGroupRefs[]`: the item's modifier groups
- `pageProps.operationalMenu.modifierGroups..label`, `.selectionMin`, `.selectionMax`, `.modifierOptionRefs[]`: modifier group
- `pageProps.operationalMenu.modifierOptions..label`, `.price`: modifier option

### Caveats

- Upstream calls change over time (embedded keys, field names). Verify responses before relying on them.
- The source site uses bot protection (AWS load balancer block for plain clients); calls may be blocked until that is handled.
- These routes were translated from working client code but have not yet been called through ApiClay. Expect adjustments once they are tested.
- Not affiliated with tbdine.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 /menu-page — Menu page (ordering page HTML)
- Gateway: `GET https://api.apiclay.com/v1/api/touchbistroapi/menu-page`
- Public query params: `orderMethod` (string, required), `venueXRefID` (string, required), `fulfillment` (string, required), `venue_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 /menus — Menus (operational menu of a venue)
- Gateway: `GET https://api.apiclay.com/v1/api/touchbistroapi/menus`
- Public query params: `orderMethod` (string, required), `venueXRefID` (string, required), `build_id` (string, required), `fulfillment` (string, required), `venue_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.

## Call example

```bash
curl -X GET "https://api.apiclay.com/v1/api/touchbistroapi/menu-page?orderMethod=<orderMethod>&venueXRefID=<venueXRefID>&fulfillment=<fulfillment>&venue_id=<venue_id>" \
  -H "token: <YOUR_APICLAY_TOKEN>"
```

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