Open API is the open programming interface available in all NETIO PDU devices (REST API, XML, JSON, Modbus/TCP, SNMP, MQTT, URL API, and other protocols).
NETIO products can be integrated with third-party products using various Open API (M2M) protocols. The NETIO Unified Open API is a set of protocols supported by all currently distributed NETIO PDUs.
NETIO Open API provides full access to control Outputs and data reading from the device. Suitable for custom integrations and automation without any "AV driver" limitations.
- Open API Usage: Requires programming, for example:
- Sending HTTP commands from your own software.
- Using Modbus/TCP in PLC systems.
- Integrating with Home Assistant or openHAB via MQTT or JSON API.
- Advantage:
- Maximum flexibility and control.
- Independent of any specific AV system.
- Open API Limitation: Requires programming skills or protocol integration experience.
NETIO unified Open API
These protocols are supported by every NETIO device:
- JSON over HTTP (default enabled protocol)
- MQTT-flex
- Modbus/TCP
- SNMP v1
- SNMP v3
- Telnet/Kshell
- URL API (http get)
- XML over HTTP
NETIO Cloud API
NETIO Cloud service connecting all NETIO devices within one user account into one device list.
All outputs can be controled via the NETIO Cloud (one API per user account).
Currently no energy measurement data are available on the NETIO Cloud API, only output electricity consumption status [Wh].
- NETIO Cloud API - MQTT
- NETIO Cloud API - REST (not available yet)
Difference between AV drivers and Open API for NETIO products
| AV drivers | Open API | |
|---|---|---|
| Target user | AV system integrators without programming knowledge | Developers and advanced integrators |
| Deployment speed | Very fast thanks to pre-prepared drivers | Requires time for programming and testing |
| Flexibility | Limited to the driver's functions | Unlimited, full access to all device functions |
| Programming knowledge required | No | Yes |