Platform & open data
The same host-keyed public JSON the storefront runs on.
Products, services, categories, staff, extras and settings are served as revisioned, cacheable JSON keyed by your domain — the exact data the storefront renders, available to whatever you build next.
Capabilities
What it does
Everything below is in the product today — not a roadmap item.
Six public data sets
Products, booking services, categories, staff, extras and settings — each served as structured JSON from public endpoints.
Keyed by your host
The shop is resolved from the request host — custom domain, alias or subdomain. Never from cookies or client headers, so the data cannot be pointed at the wrong tenant.
Revisioned responses
Responses carry a revision header, so a consumer can cache safely and know when the underlying data moved.
Per-shop isolation in the database
Isolation is enforced by row-level security in the database itself, not in the application — one shop’s data is not reachable from another.
Workflow
How it runs in real life
The same order it happens in the shop — from setting it up to closing the day.
Your domain resolves the shop
A request to your host resolves to your tenant — the same host-keyed resolution the storefront uses.
Fetch the JSON
The public endpoints return the same data the storefront renders: products, services, categories, staff, extras, settings.
Build on top
Integrations, exports, migrations or a custom front end — built on the storefront’s own data source rather than a second copy of the catalog.
The specifics
Facts, not vanity metrics
Structure facts from the product itself. No customer counts, no invented percentages.
6
public data sets — products, services, categories, staff, extras, settings
Host-keyed
tenant resolution — never cookies or client headers
Per-shop
data isolation enforced in the database
Questions
Questions about headless & api
If yours is not here, ask when you sign up — you will get a person.
It is the read-only public data layer the Vendzi storefront itself consumes, keyed by host — not a keyed write API. What the storefront can render, you can fetch.
By the request host — your custom domain, alias or subdomain. Never by cookies or client-supplied headers.
Yes. Responses are revisioned with a header, so a consumer can cache and detect when the underlying data has changed.
Run your whole front of house on one system.
Create your shop, add your services and hours, and start taking bookings today. Connect the payment provider you already use.