API
One page per procedure step, automation step, and time plan. The step is the content.
Use Guides 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.
- People / path — Person count, tiles, or Require input
- Time — usually timeline calendar
- Elements — manual or auto plan selection (optional for menu-only)
- Hold — Pre-reserve during payment
- Price — Add position and/or Order from menu, then Pay now
- Save & notify — Sync reservation / order / invoice, then guest + operator email
Topics
Usually start here