Direct Device API



  • Official comment
    Rachel Sanford

    There is no way to directly query the device to retrieve water consumption data. In order to access the data, you must use the cloud based servers. We do have a public API available that is currently in beta - if you are inerested, please visit the following address: 

  • Avatar
    Mike Schaeffer

    Thanks for the info. Several follow on questions:

    • 1) I occasionally lose internet access. Does the device have any provision for uploading water consumption data gathered during an internet outage, once network connectivity is restored?


    • 2) What kind of SLA do you provide for your web service? (Uptime, API call limits, latency of data gathering, etc.)


    • 3) What steps does your company take to ensure the privacy of water consmption data? (I'm concerned about this from a security point of view.... lower water consumption is a good way to detect an empty home.)


    • 4) What happens to the device if your company (or an acquirer, etc.) decides to discontinue the cloud service? Will it still be useful?

    I'm interested in buying two or three of these devices. A direct API makes it an easy sell. (I already have local control and monitoring software I've written running on site.)



  • Avatar
    Rachel Sanford

    Hi Mike,

    I apologize for the delayed response.

    1) Yes, StreamLabs devices store up to 3 hours of your most recent usage history.

    2) The Streamlabs API is currently in Beta and we do not have an SLA specific to it. It is currently covered by the same Streamlabs Terms and Conditions and Privacy Policy that the App and Monitor are covered under. We plan to release an SLA specific to the API for the official launch of that feature.

    3) We are currently working on a detailed and transparent article on our security practices as a supplement to our privacy policy which will answer common questions about how we transmit and store your data. We take data privacy and security extremely seriously and use industry standard TLS 1.2 end-to-end encryption wherever possible including from the Monitor to the Server and from the Server to the Streamlabs App. We host our platform using AWS infrastructure and inherit their compliance to certifications found here: We also intentionally collect only the minimum amount of personal information necessary to provide our water usage service (email, password, and zip-code if you provide it). StreamLabs does not share any of your information unless you give us permission to do so.

    4) Currently, the StreamLabs Monitor requires communication with the StreamLabs servers to operate. The StreamLabs Control can still be operated manually via the physical buttons (opening and closing the shut-off valve) without communication to our services, but the rest of its functionality would be lost.  However, we are seeing requests for a direct API and it is possible that we may add that feature in a future release.

    Hopefully we were able to answer some of your questions with the information provided above. Please let me know if you have any further questions.


Please sign in to leave a comment.