Using control API
RM1 supports the same powerful control API as all DHD products.
Please be aware that the use of our API may cause unexpected issues. DHD audio is not responsible for any problems or damages that may arise from using any API function. See full API usage disclaimer.
RM1 supports the same powerful control API as all DHD products. This API allows for comprehensive control of the audio system and seamless integration with external hardware and software.
See our control API documentation at DHD Developer Portal for endpoints and how to interact with the API.
RM1 specifics
No API token required
Since RM1 is intended to be a straightforward and user-friendly product, it does not require a token-based access control system for API access. The design prioritizes ease of use, ensuring that users can interact with the API without the added complexity of managing authentication tokens. This approach helps streamline integration while maintaining the necessary level of functionality.
On the API endpoints, you can interact with the device directly:
- On HTTP POST and GET requests, no token is needed at all. Just get or set the data.
- On websocket connections, the socket can be opened directly. No need to send the
authmethod in advance. Data can be subscribed and accessed directly.
Maximum number of concurrent connections
RM1 supports a total number of 5 websocket connections in parallel. An RM1 WebUI connection also counts towards this limitation, as well as any external API integration using websocket.