Prices and sold out from your till

1. In Settings, under API keys, tick Menus, name the key and press Make a key. Copy it now; it’s shown once.
2. In the menu editor, give each item its Code in your till (with the description, behind the three-line button beside the item) and Save. The menu’s id is under From your till.
3. Your system sends changes, for example:

curl -X POST https://dqeiiqecdxqguwrilond.supabase.co/functions/v1/api/v1/menus/MENU_ID/items \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"items": [{"code": "SKU-1042", "price_cents": 550},
                 {"code": "SKU-2001", "sold_out": true}]}'

Each line names an item by code (or its id) and gives price_cents (550 is 5.50 in the menu’s currency), prices (one per size, for categories with sizes) or sold_out. One code on several items changes them all; up to 400 lines a call. The answer says line by line what changed and what wasn’t found, and why a line didn’t fit. A line that doesn’t fit changes nothing.

Prices wait for Publish, as your own edits do. Add "publish": true to send just those prices to screens straight away; your other unpublished changes stay unpublished. Sold out is live at once, and an item that’s already sold out keeps its time, so Sold out comes back still works.

If your till changes the menu while you’re editing it, Save says so and asks you to reload first, so neither change is lost without you knowing.

Developers: GET https://dqeiiqecdxqguwrilond.supabase.co/functions/v1/api/v1/menus lists your menus and ids, GET …/menus/MENU_ID gives one with its items, and POST …/menus/MENU_ID/publish publishes.