Most digital signage buyers don't care about SDKs until they hit a wall. "Why won't this CMS read the panel's ambient light sensor?" "Why does this app eject from auto-launch every Tuesday at 3am?" The answers live in the LG webOS Signage SDK and how a given CMS actually integrates with it.
The Big Picture:
LG webOS Signage is the commercial cousin of the consumer LG TV operating system. It runs on a Linux kernel with a Chromium-based web app layer, and it exposes hardware control through three API surfaces: SCAP, IDCAP, and the Luna Bus. A real digital signage CMS that takes webOS seriously will use all three.
SCAP (Signage Common Application Platform):
SCAP is the first-party JavaScript API that LG documents publicly for signage app developers. It covers the basics: get the panel's serial number, read its model name, set/get the speaker volume, control power schedule, configure network settings, lock the OSD menu so end users can't tamper. Every commercial LG webOS Signage CMS uses SCAP. If a vendor doesn't, they're likely running a generic web app that treats the panel as a dumb display — fine for proof-of-concept, not for fleet operations.
IDCAP (Information Display Common Application Platform):
IDCAP is the deeper API. It exposes the things SCAP doesn't: panel temperature, fan speed, ambient light sensor readings, backlight hours, color calibration, USB peripheral enumeration, exact firmware version, screenshot capture from the panel itself. Crucially, IDCAP also extends to Pro:Centric — the in-room hospitality TV variant — which means a CMS built on IDCAP can drive both your lobby digital signage AND your hotel in-room TV welcome experience from one codebase.
Most SMB-tier signage vendors stop at SCAP. The ones that pursue IDCAP can offer: panel-temperature alerts (catch failing panels before they fail), accurate diagnostic screenshots (verify what's actually on the screen, not what the CMS thinks should be), backlight-hour reporting for warranty claims, and Pro:Centric integration. If you're shopping a CMS for hospitality or healthcare, IDCAP support is a real differentiator.
Luna Bus:
Luna is the inter-process message bus that LG uses internally. Some advanced operations require a Luna call rather than a SCAP/IDCAP call. Reading certain sensor values, certain panel-firmware overrides, certain diagnostics — all Luna. CMS vendors that go this deep are rare; GoVista uses Luna for panel-temperature streaming and for a handful of specific hardware quirks (some panels need a Luna call after a power-cycle to re-enable auto-launch reliably). This is the territory where vendor maturity actually shows up.
The URL Launcher Path:
LG webOS Signage has a feature called URL Launcher: configure the panel to auto-load a specific URL on boot. For digital signage that runs entirely as a PWA (no native app, no IPK install), URL Launcher is the deployment path. It's fast — under 60 seconds per panel — and zero-trust from a software-supply-chain standpoint. GoVista offers URL Launcher as one of three install paths (alongside USB-installed IPK and remote IDCAP push). Most customers use URL Launcher for pilots and IPK for production.
The IPK Install Path:
For full feature access (background sync, offline cache, watchdog behavior beyond what a PWA supports), you install a native IPK. The IPK is a signed package that LG accepts via USB stick or via the SI Server protocol. GoVista's IPK is signed; many self-hosted Xibo-style setups skip signing and have to side-load, which makes fleet management harder.
The Pro:Centric Wrinkle:
If you operate hotels, Pro:Centric is the LG OS variant for in-room TVs. It shares IDCAP with webOS Signage but has subtle differences (no SCAP-style URL Launcher, different power-management model, different update channel). A CMS that supports Pro:Centric out of the box — like GoVista — lets one team manage lobby signage AND in-room TV welcome experiences from one panel.
What to Ask LG Signage CMS Vendors in 2026:
Does your CMS use IDCAP, or only SCAP? (IDCAP = deeper hardware access.) Can your CMS read panel temperature? Backlight hours? (IDCAP-dependent.) Do you sign your IPKs, or do customers side-load? (Affects fleet manageability.) Do you support Pro:Centric in-room TV deployments? (Real differentiator for hospitality.) Can you demonstrate a panel-temperature alert path end-to-end? (Proves you actually wire IDCAP through to alerting.) The Bottom Line:
In 2026, every serious LG webOS Signage CMS uses SCAP. The ones worth paying premium for use IDCAP and Luna. The ones worth talking to for hospitality are the ones that natively support Pro:Centric on top of all three. Ask the technical questions; they reveal more about vendor maturity than any feature checklist.
