Skip to content
Docs home

CUSTOMIZATION · UPDATED AUGUST 2026

The Public Booking URL

Every tenant gets a public booking surface at /u/:slug — validated server-side, token-managed, and brandable.

What the surface is

The public booking URL is the customer-facing home of a business on QUE: https://que.qubickle.com/u/your-slug. Every request validates that the tenant exists and is publicly visible, then renders the business's services, availability, and branding. Customers book here; staff log in here through the tenant login route; customers manage existing bookings here through their token links.

Server-side validation

Tenant visibility and booking eligibility are validated server-side on every request — not assumed from the URL. A deleted, hidden, or ineligible tenant renders its booking surface as unavailable rather than leaking internal state. Booking management links (cancel/reschedule) carry tokens that are validated alongside the tenant on every use.

Token-based management

Customers do not need accounts to manage their bookings. The confirmation view includes a management link whose token authenticates the specific booking: cancel and reschedule endpoints validate the token and return typed results. A token for one tenant's booking cannot address another tenant's data.

Own your surface

The booking URL is the business's public face. Combine it with a custom domain and the embed script to make booking feel native to the business — same engine, the business's identity.

STILL READING

Something here still feels worth checking together.

This documentation describes the product exactly as it is implemented. If a behavior you expected is not here — or is here and does not match your deployment — tell the team. Implementation questions start on the contact page.