SmartyPOS

An API a single restaurant can write to.

Syrve documents its Cloud and server APIs publicly. A restaurant, or the team it hires, can read data and change it: prices, menu cards, schedules, loyalty, orders.

Live

What we do with it every week

Price change orders

Raise or align prices through the API, set lunch prices on a schedule, fill aggregator price categories (for example Uber Eats plus 25%). Thirteen price orders have gone through for Food Court Master.

Time clock fixes

Find and close forgotten clock-outs and reconcile payroll to the cent against the POS (Brisket, 1 to 15 November).

Menu and tax setup

Full launch for Food Court Master: menu, recipes, an 11% tax on 387 items, Cloud API and a 226-item external menu.

Orders in

Our ordering sites and Deliverect push orders into Syrve; duplicates and ghost orders are blocked.

Compared with a read-only API

On Toast, a restaurant gets the Standard API for reading data. Writing needs partner approval, and Toast declined it for a single location of ours on 2026-07-12. That is why this page exists: if you want software to run parts of your restaurant, check the write path before you buy.

Syrve's authentication is moving to a newer token flow; we handle the migration for the services we maintain.

Frequently asked questions

Do I need to be a developer?

No. We build and run integrations for you. The API matters because it means you are never waiting for a vendor to add what you need.

Is the API documented?

Yes, Syrve publishes the Cloud API specification openly and we keep a local copy to work from.

See it on your menu, your orders, your numbers.

A 45-minute call. We open Syrve with your concept in mind, show what is live today, and tell you straight whether it fits.