# Talech API

> Talech online ordering microsite menus, product variations and add-ons

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

## About

## Talech API

Read the online-ordering menu of a restaurant or shop that uses a Talech ordering microsite (categories, products, prices, order types) and the variations and add-on groups of any product.

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

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

A Talech ordering URL looks like `microsite.talech.com/ordering//`.

`/menus` reads Talech's Next.js data file, whose path contains a build id that changes every time Talech deploys. Read the current `buildId` from the `__NEXT_DATA__` script in `/menu-page` and pass it as `build_id`. The same page props are also embedded in that script, so `/menu-page` alone can be enough.

### Routes

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

| Param | In | Type | Required | Description |
|---|---|---|---|---|
| slug | path | string | yes | Merchant slug from the ordering URL. |
| merchant_id | path | string | yes | Merchant id from the ordering URL. |

Returns: HTML. In `__NEXT_DATA__`: `buildId` (for `/menus`) and `props.pageProps.data` (the same data `/menus` returns).

#### GET `/menus` - Menus (online ordering menu)
Returns the merchant'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 Talech deploy. |
| slug | path | string | yes | Merchant slug from the ordering URL. |
| merchant_id | path | string | yes | Merchant id from the ordering URL. |
| id | query | string | yes | Same value as `merchant_id`. |

Returns (fields read by the source code; not yet verified live):
- `pageProps.data.merchant.onlineOrdering.orderTypes[].label`, `.isEnabled`: Pickup / Delivery availability
- `pageProps.data.categories[].id`, `.name`: category
- `pageProps.data.categories[].products[].id`, `.name`, `.description`, `.price`, `.image`: product (price in dollars)

#### GET `/customizations` - Customizations (variations and add-ons of a product)
Returns one product's variations, variants and add-on groups.

| Param | In | Type | Required | Description |
|---|---|---|---|---|
| merchant_id | path | string | yes | Merchant id from the ordering URL. |
| item_id | path | string | yes | Product `id` from `/menus`. |

Returns (fields read by the source code; not yet verified live):
- `data.variations[].id`, `.name`, `.options[].id`, `.name`: variation choices (e.g. size)
- `data.variants[].variationOptions`, `.price`, `.productId`: price of each variation combination
- `data.addOns[].id`, `.name`, `.position`, `.settings.minSelection`, `.settings.maxSelection`: add-on group
- `data.addOns[].options[].id`, `.name`, `.price`: add-on option

### Caveats

- Upstream calls change over time (embedded keys, field names). Verify responses before relying on them.
- No live Talech ordering microsite was found to test against, so the routes have not been checked yet.
- 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 talech.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/talechapi/menu-page`
- Public query params: `slug` (string, required), `merchant_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 (online ordering menu)
- Gateway: `GET https://api.apiclay.com/v1/api/talechapi/menus`
- Public query params: `id` (string, required), `build_id` (string, required), `slug` (string, required), `merchant_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 /customizations — Customizations (variations and add-ons of a product)
- Gateway: `GET https://api.apiclay.com/v1/api/talechapi/customizations`
- Public query params: `merchant_id` (string, required), `item_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/talechapi/menu-page?slug=<slug>&merchant_id=<merchant_id>" \
  -H "token: <YOUR_APICLAY_TOKEN>"
```

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