Low Code Video

EnableX Low Code Video is a fully hosted video conferencing application that runs on a subdomain you control — https://YOUR_SUBDOMAIN.yourvideo.live. There is nothing to build or deploy. You configure it once through a three-step wizard, and your video application is live. Users join from a browser or an embedded IFRAME using a direct URL. No SDK integration is required on your side.

The application is highly customisable. You choose a starting template, define which features are active, control the look and feel through a visual builder, and can further override any setting at runtime using URL query parameters. For more advanced use cases, the embedded session can communicate bidirectionally with the parent web page through postMessage.

Once you have a Video Project, setting up Low Code takes a few minutes in the EnableX Portal. The wizard walks you through three steps — template selection, subdomain creation, and a quick verification — after which your video application is ready to use.

Step 1 — Choose a Template

EnableX provides a library of pre-built templates tailored for common use cases such as virtual classrooms, telehealth consultations, corporate meetings, and webinars. Each template ships with a curated set of tools and UI layout appropriate for that use case.

If none of the ready-made templates fit your requirements, a Build from Scratch option lets you start with a blank canvas and assemble exactly the features you need.

Step 2 — Create a Subdomain

Enter a unique subdomain name. Your Low Code application will be accessible at:

https://YOUR_SUBDOMAIN.yourvideo.live

The subdomain is globally unique — if the name is already taken, you will be prompted to choose another. Once created, all direct join URLs and IFRAME embed codes are automatically qualified with this subdomain. The subdomain uses your Video Project's access credentials without any additional configuration.

Step 3 — Verify and Get Your Links

The final step confirms that your Low Code application is live and hands you everything you need to start using it:

• Try it now — A quick-launch option opens the video session directly in the portal so you can verify the experience before sharing any links.
• Direct join URLs — Role-specific URLs for Moderators, Participants, and HLS Audience. Share these links directly or embed them in your application. See Join URL Patterns below.
• IFRAME embed codes — Ready-to-paste HTML snippets using the direct join URLs as the src. Copy and drop into any HTTPS-hosted webpage.

Default Room

When your Low Code application is set up, EnableX automatically provisions a Default Room for it. The join URLs generated in Step 3 reference this room. You can use the Default Room immediately for testing or as your primary meeting room.

Additional Rooms

A single Low Code subdomain can serve multiple rooms. Each room has its own Room ID and therefore its own set of join URLs, but they all share the same subdomain, UI configuration, and feature set. This lets you run parallel video sessions — for example, separate virtual classrooms or concurrent meeting breakouts — all under one Low Code application.

Additional rooms are created using the Video API (Room Management). Once a Room ID is available, substitute it into the URL patterns described below.

Every video session in a Low Code application is accessed through a role-specific URL. The URL encodes both the destination subdomain and the Room ID (or a signed hash for moderators). There are three URL patterns — one for each role:

Participant URL

A standard participant joins using a URL that contains the Room ID directly:

https://YOUR_SUBDOMAIN.yourvideo.live/ROOM_ID

Participants have access to audio, video, chat, screen sharing, and all other features enabled for the room. They cannot moderate the session or perform administrative actions.

HLS Audience URL

When a session is live-streamed using HLS, viewers who are not participating in the conference watch via a dedicated stream URL:

https://YOUR_SUBDOMAIN.yourvideo.live/stream/ROOM_ID

The audience viewer receives a one-way video stream. They do not send audio or video and do not appear in the participant list. This URL is only active when a moderator has started HLS streaming for the session.

Moderator URL

Moderators join using a URL that contains a signed hash instead of a plain Room ID. This prevents unprivileged users from claiming moderator access simply by guessing a URL:

https://YOUR_SUBDOMAIN.yourvideo.live/host/HASH

The HASH is a Base64-encoded string formed by concatenating the Room ID and the App ID with a dash as a separator:

HASH = base64_encode( ROOM_ID + "-" + APP_ID )

The App ID comes from the Video Project the Low Code application belongs to. Because the hash encodes both identifiers, only someone who knows both values can construct a valid moderator link.

Moderators have the following privileges over and above a standard participant:

• Lock and unlock the room
• Record the session
• Start and stop HLS live streaming
• Mute the entire room
• Hard mute an individual participant's audio or video
• Disconnect a participant from the session
• Control participant entry (waiting lobby)
• End the conference for all participants

IFRAME Embed

Any of the three join URLs can be used as the src of an HTML IFRAME. Drop the snippet below into any HTTPS-hosted webpage and replace the placeholder with the appropriate URL for the role:

<iframe
  allow="camera; microphone; fullscreen; speaker; display-capture"
  src="https://YOUR_SUBDOMAIN.yourvideo.live/ROOM_ID"
  width="100%" height="100%" frameborder="0">
</iframe>

Mobile and Native Application Embed

Low Code join URLs work equally well inside native mobile applications using platform webviews:

• Android — Use WebView. Override WebChromeClient.onPermissionRequest to grant camera and microphone access, and append ?skipMediaPermissionPrompt to the URL so the in-session permission dialog is skipped.
• iOS — Use WKWebView (iOS 14.5+) or SFSafariViewController (iOS 14.3+). Add NSCameraUsageDescription and NSMicrophoneUsageDescription keys to your app's Info.plist.
• React Native — Request camera and microphone permissions at runtime using expo-permissions before loading the webview.
• Flutter — Use flutter_inappwebview with permission_handler. Handle androidOnPermissionRequest to grant media access at runtime.

Setting up Low Code is the beginning, not the end. Once the subdomain is live, the application is fully configurable:

• Visual Builder — Modify the UI template from the portal at any time. Control screen layout, toolbar composition, information display, and branding (logo, colours). Changes apply globally to all sessions on that subdomain.
• Query String Parameters — Override individual features or UI settings per URL at runtime, without changing the Visual Builder configuration. Useful for passing participant names, enabling or disabling specific features for a session, or customising the waiting lobby experience. See Query Parameters.
• Parent Window Communication — Exchange data and trigger actions between the embedded IFRAME and the hosting page using postMessage. The embed can notify the parent when a participant joins or leaves, when recording starts, or when the session ends. The parent can instruct the embed to start streaming, send chat messages, or disconnect participants. See Parent Window Communication.
• Multiple Rooms — Create additional rooms via the Video API and generate role-specific join URLs for each. All rooms share the same UI configuration and subdomain. See Room & Join Links.