Display Feature Flags
Section titled “Display Feature Flags”The HTML5 display client exposes a set of feature flags that toggle optional session capabilities: printing, file transfer, video playback (including the MediaSource API path), and notifications. Pass these as query parameters on the display client URL to enable, disable, or configure each capability per session.
This page documents the feature toggle parameters accepted by the display client endpoint. Other client parameters (display selection, encoding, keyboard, debugging, and so on) are documented on their respective pages.
GET /api/v1/display/
Section titled “GET /api/v1/display/”Serves the HTML5 Display client web interface with optional URL-based configuration. This is the API-versioned equivalent of the root display endpoint and accepts the same query parameters for full client customization.
Use this endpoint for RESTful API compliance, versioned client access, and API gateway integrations. The endpoint accepts 50+ URL parameters; only the feature toggle parameters are documented here.
Parameters
Section titled “Parameters”| Name | In | Type | Required | Description |
|---|---|---|---|---|
printing | query | boolean | No | Enable printing support. Default: true |
file_transfer | query | boolean | No | Enable file transfer support. Default: true |
video | query | boolean | No | Enable video encoding support. Default: true |
mediasource_video | query | boolean | No | Enable MediaSource API for video. Default: true |
notification_server_url | query | string | No | External notification server URL for real-time notification integration. |
web_notifications | query | boolean | No | Enable browser web notifications (native OS notifications). Default: true |
display_notifications | query | boolean | No | Show notifications within display UI. Default: true |
notification_connection_type | query | string | No | Notification server connection type. Allowed values: websocket, polling. Default: "websocket" |
Request
Section titled “Request”This endpoint takes no request body.
Examples
Section titled “Examples”curl -G "https://my-project-my-container-display-1.node.containers.hoody.icu/api/v1/display/" \ --data-urlencode "printing=true" \ --data-urlencode "file_transfer=true" \ --data-urlencode "video=true" \ --data-urlencode "mediasource_video=true" \ --data-urlencode "notification_server_url=https://my-project-my-container-n-6.node.containers.hoody.icu/notification-client.js" \ --data-urlencode "web_notifications=true" \ --data-urlencode "display_notifications=true" \ --data-urlencode "notification_connection_type=websocket"import { HoodyClient } from "hoody-sdk";
const client = new HoodyClient({ token: process.env.HOODY_TOKEN });
const html = await client.display.accessClient({ printing: true, file_transfer: true, video: true, mediasource_video: true, notification_server_url: "https://my-project-my-container-n-6.node.containers.hoody.icu/notification-client.js", web_notifications: true, display_notifications: true, notification_connection_type: "websocket",});Response
Section titled “Response”HTML5 Display client interface loaded successfully. The response body is the HTML5 client markup, served with content type text/html.
<!DOCTYPE html><html><head><title>Hoody Display Client</title></head><body> <!-- Display HTML5 client interface --></body></html>