Last updated: Sep 11, 2026
Manifest
At its core, every OvrC Integration boils down to just two files:
integration.{ext}1manifest.json
The manifest.json file provides OvrC with information necessary
to properly run and expose an integration to users.
The full manifest.json JSON Schema definition can be found here.
Some of the fields and data the manifest.json file exposes include:
| Field Name | Description | Type |
|---|---|---|
| category | Integration category. | enum: display, camera |
| description | Human-readable integration description. Example: Integration for Samsung TVs. | string |
| identification | object | |
| kind | The kind of integration associated with this manifest. | enum: wasm, js |
| name | Human-readable integration name. Example: Samsung TV | string |
| version | Semantic version of the integration. Example: 1.0.0 | string |
Manifest Fields
The following dives deeper into some of the fields defined
in a manifest.json file.
identification
The identification field contains data used to identify devices with which the integration is compatible. See matching for more details regarding identification and discovery.
One of the fields within the identification object is discovery.
The discovery field serves as a declarative mechanism
for matching an integration to a device, based on data
received from the device using common protocols.
Some examples of such protocols include: UPnP, SDDP, PJLink, etc… The integration manifest must specify one or more discovery protocols.
The list of currently supported protocols/fields include:
- dnssd
- mac_oui
- mdns
- onvif
- pjlink
- sddp
- snmp
- ssdp
- upnp
- wsdiscovery
Manifest Testing
Tools for creating and testing a manifest.json file can be found within
the OvrC Integration Developer Mode.
-
currently supported extensions are:
js. ↩