API

One page per procedure step, automation step, and time plan. The step is the content.

Use How to when you need an outcome built from several steps. Use Examples for a complete procedure template. Each API page lists Commonly used with when related steps or examples are known.

Build a booking flow

Most live procedures follow one spine. Add steps in this order, then open the matching group below.

1. People / path — Person count, tiles, or Require input
2. Time — usually timeline calendar
3. Elements — manual or auto plan selection (optional for menu-only)
4. Hold — Pre-reserve during payment
5. Price — Add position and/or Order from menu, then Pay now
6. Save & notify — Sync reservation / order / invoice, then guest + operator email