Web Client Interface
Configure the HTML5 display client, including the WebSocket transport, scaling, and client-side rendering options.
The Display service provides a browser-based HTML5 viewer for remote desktops and applications running inside a Hoody container. It handles everything between the running workload and the user’s browser tab: rendering, encoding, input, screenshots, and session control. Every endpoint documented under this section is scoped to a single container and is reachable over HTTPS at the container’s display subdomain.
This section is organized around the responsibilities of the display server. Configuration endpoints live alongside the runtime endpoints they affect, so most workflows only need two or three pages.
Web Client Interface
Configure the HTML5 display client, including the WebSocket transport, scaling, and client-side rendering options.
Input and Clipboard
Configure keyboard layouts, clipboard sharing, and scroll behavior between the local browser and the remote session.
Input Actions
Send low-level mouse, keyboard, and window-management events to automate or script the remote display.
Screenshots
Capture still images and thumbnails of the current display frame buffer and manage stored captures.
Session and Sharing
Configure session sharing, read-only mode, and guest access policies for the active display session.
Health and Info
Read service health, version information, and the live API documentation exposed by the display server.
Performance and Encoding
Tune codec selection, frame rate, bandwidth ceilings, and rendering quality for the display stream.
UI and Theming
Configure window decorations, the in-browser toolbar, and dark mode appearance for the viewer.
Feature Flags
Enable or disable individual features such as printing, file transfer, audio, and video playback.
Debugging
Enable diagnostic flags and verbose logging when troubleshooting display or streaming issues.
All endpoints in this section are served by a per-container display server. Substitute {projectId}, {containerId} and {server} with the project, container and server of the target workload; the -display-N segment selects the display:
https://{projectId}-{containerId}-display-1.{server}.containers.hoody.comA request to the root path returns the HTML5 client. API endpoints are mounted under /api/... paths on the same host and accept a bearer token in the Authorization header.