API documentation.
Two ways to put Restzo's data in front of customers: embed our widget on an existing site, or build your own frontend against the headless CMS API.
Both are read-mostly, key-authenticated (a publishable key per tenant, no OAuth/login), CORS-open, and JSON over HTTPS. Pick based on how much of the frontend you want to own:
Widget Embed
Drop-in embeddable menu + booking widget for a tenant's own existing website — one <script> tag, zero frontend code.
Headless CMS
Build your own bespoke frontend entirely and pull raw menu/site/inquiry data from our API — full control, no embed.
Not sure which one fits? If a tenant already has a website (WordPress, Webflow, a custom build) and just wants a menu/booking widget on it, use Widget Embed. If a tenant (or their developer) is building a fully custom site from scratch and wants to own every pixel, use Headless CMS.