MenuNode for developers
Connect a POS, stock, delivery or an automation to a restaurant on MenuNode. Everything below works today and is described in the OpenAPI specification.
Open the OpenAPI specification
The API (/api/v1)
A REST API for one restaurant: read the menu, orders, bookings and reviews, and change prices or sold-out dishes. The base URL is https://menunode.com/api/v1.
- Every call sends
Authorization: Bearer <key>. Dashboard cookies never work with this API. - Limit: 120 calls per minute per key. Each answer carries
X-RateLimit-Limit,X-RateLimit-RemainingandX-RateLimit-Reset; past it, 429 withRetry-After. - Errors always look like
{"error": {"code": "...", "message": "..."}}. An id of another restaurant answers 404, just like one that does not exist. A method the path does not take answers 405 with anAllowheader. - Amounts are strings with two decimals (
"12.50") in the restaurant’s currency. - Lists come in pages: send the answer’s
next_cursorascursorto get the next one.
curl https://menunode.com/api/v1/restaurant \
-H "Authorization: Bearer pat_…"| Path | Method | What it does | Permission |
|---|---|---|---|
/restaurant | GET | The restaurant of the key. Works with any permission. | — |
/hours | GET | Opening hours, special days, ordering hours and booking rules of one location (branch_id). | — |
/menu | GET | The whole menu with the price and availability right now. | menu:read |
/items/{id} | PATCH | Change a dish price or mark it sold out (sold_out_today, sold_out, available). | menu:write |
/orders | GET | Confirmed orders, newest first, filtered by date, status and payment. | orders:read |
/order-links | POST | A link to the order page with the cart filled in: the guest confirms and pays there. | menu:read |
/reservations | GET | Confirmed bookings in calendar order. | reservations:read |
/reviews | GET | Guests’ answers to "How was it?". | reviews:read |
/webhooks | GET POST | List and create webhook endpoints. | webhooks:write |
/webhooks/{id} | GET PATCH DELETE | Read, change (events, location, pause) or delete an endpoint. | webhooks:write |
/webhooks/{id}/test · /rotate-secret | POST | Send a test event or change the signing secret. | webhooks:write |
/webhooks/{id}/deliveries · …/resend | GET POST | Delivery log, and resend one. | webhooks:write |
/feeds/menu.json · /feeds/menu.csv | GET | The menu in fixed columns, JSON or CSV, hidden dishes included. | menu:read |
Getting a key
The owner creates it in the dashboard, in Settings → Integrations → API for integrations: a name and the permissions. The key starts with pat_ and is shown once; MenuNode only keeps its fingerprint, so a lost key is replaced by a new one and the old one deleted.
- A key belongs to one restaurant. No parameter points it at another.
- A write permission includes the read one (
menu:writealso reads the menu). - A key for one location only sees that location’s orders and bookings. It cannot change the price or sold-out state of the whole menu (403
branch_scoped) nor manage webhooks (403branch_token_not_allowed).
| Permission | What it does |
|---|---|
menu:read | Read the menu, the hours and the menu files. |
menu:write | The above, plus changing prices and sold-out dishes. |
orders:read | Read orders and receive the order and table bill events. |
reservations:read | Read bookings and the waitlist. |
reviews:read | Read reviews (they carry the guest’s name and email). |
webhooks:write | Create and manage webhook endpoints. |
MCP servers for AI assistants
MCP is the protocol an AI assistant (Claude, ChatGPT and others) uses to call tools. MenuNode has two servers.
The public one, at https://menunode.com/mcp, needs no key. It finds restaurants, reads their menu and details, asks something the menu does not answer, shows free times and, where the restaurant turned it on, orders, books or joins the waitlist. Orders, bookings and the waitlist are always confirmed with a 6-digit code emailed to the guest.
- Reading:
search_restaurants,get_restaurant_info,get_menu,get_menu_structured(withavoid, the allergens the guest avoids),quote_group,list_available_slots,check_availability. - Orders:
prepare_order_link,create_orderandconfirm_order,get_order_status. - Bookings:
create_reservationandconfirm_reservation,get_reservation,change_reservation,cancel_reservation,create_availability_alertandconfirm_availability_alert. - Waitlist:
get_waitlist_status,join_waitlistandconfirm_waitlist,get_waitlist_position,leave_waitlist. - Questions:
ask_restaurant(the restaurant’s answer is published inget_restaurant_info).
The owner’s one, at https://menunode.com/mcp/owner, needs a key (Authorization: Bearer pat_…). With menu:write the assistant builds and edits the menu: sections, dishes, scheduled prices, sold out, translations, importing a menu from text (import_menu_from_raw_text) or loading it whole (bulk_upsert_menu). Other tools ask for their own permission: orders and bookings (orders:read, orders:status, reservations:read, reservations:status), reviews, customers (customers:read), the waitlist, pausing orders, special days and menu numbers. In the dashboard, Settings → Integrations → Teach your AI to use your restaurant makes the key and the steps to connect it.
Webhooks to your system
MenuNode POSTs to an https address of yours whenever something happens. Register it in the dashboard (Settings → Integrations) or with POST /webhooks. Up to 10 addresses per restaurant; each picks its events and, when the restaurant has several locations, one of them: it then gets that location’s orders, bookings, waitlist, bills, hours, reviews and sold-out dishes, plus changes to the whole menu.
The body is {id, type, api_version, timestamp, restaurant_id, data}. A key can only subscribe to events it could read with its permissions.
- To tie an address to one location: pick it under "Which place" in the dashboard, or send
branch_idwhen creating or changing the address (null= every location). - Signature (Standard Webhooks): the headers
webhook-id,webhook-timestampandwebhook-signature. The signature isv1,plus the base64 HMAC-SHA256 ofid.timestamp.body, keyed with the base64 part of yourwhsec_…secret. Reject times more than 5 minutes off. - Answer 2XX within 10 seconds. Otherwise it is retried 5 times (1 min, 5 min, 30 min, 2 h and 12 h) with the same
webhook-id: use it to skip duplicates. Redirects are not followed. - An address that answers 410, or keeps failing for over a day, is switched off and the owner gets an email.
menu.updatedis batched: many edits in a row send one, about a minute after the last (at most 5 minutes after the first).hours.updatedis batched per location for about 10 seconds.- From the dashboard or the API you can send a test event, see the latest deliveries and resend one. The signing secret is shown once; if lost, change it for a new one.
const { createHmac, timingSafeEqual } = require('node:crypto');
// headers: the request headers; rawBody: the body exactly as received (before JSON.parse).
function verify(secret, headers, rawBody) {
const id = headers['webhook-id'];
const ts = headers['webhook-timestamp'];
if (Math.abs(Date.now() / 1000 - Number(ts)) > 300) return false;
const key = Buffer.from(secret.slice('whsec_'.length), 'base64');
const expected = createHmac('sha256', key).update(id + '.' + ts + '.' + rawBody).digest();
return headers['webhook-signature'].split(' ').some((part) => {
const given = Buffer.from(part.split(',')[1] ?? '', 'base64');
return part.startsWith('v1,') && given.length === expected.length && timingSafeEqual(given, expected);
});
}| Event | What it does | Permission |
|---|---|---|
order.created | New order | orders:read |
order.status_changed | Order status change | orders:read |
reservation.created | New reservation | reservations:read |
reservation.updated | Reservation changes | reservations:read |
waitlist.joined | Someone joined the waitlist | reservations:read |
waitlist.updated | Waitlist changes | reservations:read |
menu.updated | Menu changes (grouped per minute) | menu:read |
item.sold_out | Dish sold out | menu:read |
item.available | Dish available again | menu:read |
order.payment_changed | Order payment (reported, received, refunded) | orders:read |
hours.updated | Hours changed | menu:read |
review.received | New review received | reviews:read |
order.updated | Order changed (a dish is missing or was taken off) | orders:read |
bill.issued | A table bill was made | orders:read |
bill.paid | A table bill was paid | orders:read |
bill.voided | A table bill was voided | orders:read |
Menu files and calendar
- Public, no key:
/m/<restaurant>/menu.jsonand/m/<restaurant>/menu.csv, with what the menu shows (langfor the language,branchfor a location). - With a
menu:readkey:/api/v1/feeds/menu.jsonand.csv, hidden dishes included,branch_idfor a location.format=metareturns the Meta catalog format (WhatsApp and Instagram). - A bookings calendar (.ics) at a secret address the owner creates and revokes in the dashboard.
- The files answer
ETagand 304 when nothing changed.
Recipes for n8n and Make
To automate without code. In the dashboard, Settings → Integrations, each recipe downloads a template for n8n or Make and connects it to an event:
- Each new order to a Google sheet (
order.created). - Each new booking to a Telegram group (
reservation.created). - Each new order by email to someone else (
order.created). - Each order payment to a Google sheet (
order.payment_changed). - Each change of hours by email to whoever updates your other pages (
hours.updated).
The n8n templates come with an address of their own for each download.
Missing something?
If an integration needs data or a path that is not there, write to us from contact or at support@menunode.com.