Jump to content
Monthly Subscriptions Are Here Read more... ×
Sign in to follow this  

Let's start discussing about possible usage of Domotz Public API

Recommended Posts


As you might be aware, in Q4 2018 we opened our cloud-based RESTful API to the public to be used by Domotz Users to get information out of our cloud or update configuration or more.


Any developers has now have an easy and comprehensive way to integrate third party applications with the Domotz Pro solution for several purposes. E.g.:


  • Custom Dashboards: you can build your own dashboard to show the status of all the devices you are monitoring for your customers, and you can enrich it with your own data
  • Asset Management: you can build your own Asset Management tool. In an instant, you can retrieve the enriched list of all the devices online/offline in any single network you monitor and manage through Domotz
  • Customized Reports: create your customized reports and provide them to your customers. You can create and host on your servers script to extract data out of Domotz and prepare PDF or XLS sheet you can finalize with your own data
  • Identify the most trouble device: create your custom script to extract the most troubled devices among all your Agents for example by identifying which one drops out of the network the most often
  • self-healing script: write your own script that reboot a device (either through the connected PDU or PoE port of the switch, or through soft reboot) in the case it is discovered offline
  • much more: the only limit is your imagination


We will use this area of the forum to post open source code, developed using the Domotz Public API and to get feedback on those.


Please, use this section also to ask questions or advices on how to best use the Domotz Public API for your specific use cases.


For reference, Documentation related to the latest version of the Public API is available here.

Share this post

Link to post
Share on other sites

First of all, thanks very much for this!


I would love to be able to do a REST streaming call which would return device status changes (JSON) as they happen.  This is better for both sides, since it's a nailed-up connection, we avoid the overhead of connection setup and time delay between polling cycles.  

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this