Public help-center surfaces
These reads back a tenant’s customer-facing help center — pages any visitor loads before they sign in. For support-operations teams that publish a public portal, this pair is the read side of the CXaaS help surface: branding paints the tenant’s white-label look, and the ticket-status endpoint lets the visitor check progress on their submission. Theorg query names the organization slug; no API key is required, and the surfaces are rate-limited per source IP.
GET /api/v1/public/help/branding returns the public-safe help-theme subset.
show_powered_by defaults to true until the tenant opts out of the Orbit credit. Only the help-theme subset is exposed — never the broader dashboard branding, support email, or custom-domain config.
GET /api/v1/public/help/tickets/{id}?org=&token= returns the requester’s view of one public-form ticket. The receipt token issued at submit is a bearer capability over that ticket id, and any miss (wrong org, wrong token, or an ID for an internal-only ticket) collapses into a generic 404 so the endpoint never enumerates existence.
status reads as one of open, pending, resolved, or wont_fix; comments exposes only public-visibility replies, never operator internal notes.