Skip to main content

Customize Applications

Orchestra exposes internal APIs that let you build tailored staff workstation interfaces and operational tooling beyond what the standard Qmatic applications provide. Unlike the Calendar Public API, these APIs are staff-facing — they are not intended to be called from customer-facing surfaces.

What you can build​

Custom counter terminals — replace or supplement the default Orchestra staff terminal with a bespoke UI that fits your workflow, branding, or hardware constraints. Call tickets, handle transfers, create walkdirects, and manage multi-service visits through the Counter API.

Operational dashboards — query queue depth, waiting times, and visit parameters in real time. Surface this data in custom displays, supervisor views, or third-party reporting tools.

Authentication model​

Internal Orchestra APIs use HTTP Basic Auth on every request, plus a server-issued session cookie that must be included on all subsequent calls. This is separate from the OAuth2 / API Gateway flow used by the public APIs. See the individual guide for session management details.

Not for customer-facing use

Do not expose these internal API endpoints to untrusted clients or public networks. Route them through your own backend if you need to power a customer-facing UI.

Guides​