Build on Tably.The POS, as an API.

A REST API for orders, menu, customers, team, stock, money and reports; signed webhooks for what happens on the floor and in the kitchen; and an MCP server, so an AI assistant can run it too.

55endpoints
20webhook events
MCPfor AI assistants
OpenAPI3.1 spec
Create an order
curl -X POST https://tablypos.com/api/v1/open/orders \
  -H "Authorization: Bearer $TABLY_KEY" \
  -H "Content-Type: application/json" \
  -d '{"service":"table","table":"4",
       "items":[{"dishId":"pad-thai","quantity":2},
                {"dishId":"iced-latte",
                 "modifiers":[{"groupId":"milk","optionId":"oat"}]}]}'
Response · on the kitchen screen a second later
{
  "id": "API-MFX2K91", "number": 12, "status": "open",
  "table": "4",
  "items": [{ "name": "Pad Thai", "quantity": 2, "price": 6.50 }],
  "subtotal": 13.00
}

Start in three steps

1Get a key

In Tably: Settings → Integrations → New key. Read only for reports, read & write to create orders. Part of the plans with API & integrations.

2Make a call

GET /restaurant checks the key; GET /menu gives the dish and modifier ids. Or press Try it in the reference — no code at all.

3Listen

Add a webhook and Tably calls your server the moment an order is paid, a dish is ready or stock runs low — signed, retried.

What people build with it

Websites, delivery services, accounting and dashboards — anything that should know what happens in the restaurant, or tell it.

Online ordering

Your website takes the order; POST /orders puts it on the kitchen display and the waiters’ tablets, POST /payments closes it.

Delivery apps

Orders from a delivery service land in Tably like any other — the kitchen cooks them, the receipt and the stock follow.

Accounting

order.paid and shift.closed send every receipt and cash count to your books; POST /transactions brings the bank’s bills and income back into Tably.

Loyalty

Create customers from your app, give them a discount, see what they order.

Live dashboards

Open orders, tables busy, the day’s sales by hour — for a screen in the office or a chain’s HQ.

Purchasing

stock.low the moment an ingredient goes under its minimum; order from the supplier, and POST /supplies puts the delivery in — a draft to check, or received.

Safe by design

Keys are hashed and shown once. A write key changes only what you allow it (orders, customers, menu, stock, money), every change is in the history with the key’s name, and externalId makes a retry safe. 120 requests a minute; webhooks only to public https addresses.