API access

Comments

16 comments

  • Official comment
    Avatar
    Rachel S

     Hello everyone,

    We're excited to announce the launch of our API Beta program! Head on over to our new Streamlabs API forum to join the discussion and learn more about what the API entails.

    Thank you all for your valuable feedback and ideas! The discussion in this thread was key in the development of our API program, and we are very excited to provide it for you!

    Comment actions Permalink
  • Avatar
    Domnick Eger

    I have a feeling a public API going to be a pain for them to release since they are using the AWS Security Token Service and the request will cost them over a long period of time if the customer tries to poll this after 60 seconds. I guess it back to the drawing board unless there a local interface page I can scrap for details. Really love the product and it a great idea but the lack of an API sucks :(


    -H ' Host: api.streamlabs.io'
    -H 'accept: application/json'
    -H 'content-type: application/json'
    -H 'x-amz-security-token: '
    -H 'accept-language: en-us'
    -H 'x-amz-date: 20180407T041809Z'
    -H 'utc-offset: -7'
    -H 'user-agent: aws-sdk-iOS/2.6.1 iOS/11.2.6 en_US'
    -H 'authorization: AWS4-HMAC-SHA256 Credential=, SignedHeaders=accept;content-type;host;user-agent;utc-offset;x-amz-date;x-amz-security-token, Signature=' --compressed 'https://api.streamlabs.io/v1/locations/$$$$$/trends'

    1
    Comment actions Permalink
  • Avatar
    Domnick Eger

    I second an public API

    0
    Comment actions Permalink
  • Avatar
    Zellux

    Yeah without an API the only use case of the device for me right now is leak detection, a public API would be great so we can integrate it with other services.

    0
    Comment actions Permalink
  • Avatar
    Domnick Eger
    0
    Comment actions Permalink
  • Avatar
    Zellux

    Good point, alternatively maybe they can provide a callback option, which sends data from mobile app to your own server. It increase burden on user side but at least it won't cost them extra server traffic.

    0
    Comment actions Permalink
  • Avatar
    Alex S

    At least building an IFTTT connector might be a simpler alternative.

    0
    Comment actions Permalink
  • Avatar
    Michael Smith

    Oy.  Really, An API, or other ways to integrate this is so obviously needed.  The fact that it wasn't part of their plan is troublesome.  

    How about start with something really simple...  Send read-only stuff like consumption/flow rate every minute over udp to a local IP address.  Requires no authentication.  Expose more data, and maybe let us set home/away with websockets and a very simple auth like a key.  Again. fine for local use.  Then IFTTT and finally a real public REST API.  But do something.

    0
    Comment actions Permalink
  • Avatar
    Benoît P

    Hi,

    I'm really interested in an open REST API too !

    I want to integrate it to :

    - Home Assistant for better automation / alerting (MQTT integration would be great too in addition of the REST API)
    - InfluxDB + Grafana for good graphing

    If the API is local (ie. hosted on the device as we can find on many home bridges) it would be better for privacy, product life cycle, performances.

     

    0
    Comment actions Permalink
  • Avatar
    Brad Anderson

    Hi,

    I am on the fence for purchase of this device, looking into whats out there in water monitors, an open API (local to unit sounds great) would defiantly sell this unit for me. 

    It would be a shame to stop just short of greatness.

    -Brad.

     

     

    0
    Comment actions Permalink
  • Avatar
    UiGuy

    IoT is all about BIG Data and then combining, mashing that data to drive smart (even AI) automations... using your phone to control stuff is not smart... is is just another remote control....

    Break down the "walled gardens" give users access to their data.... 

    ...give me an API and I will start selling these as part of the (Global) Telco I work for's IoT product offering for which I am the product owner...

    0
    Comment actions Permalink
  • Avatar
    Steven Taylor

    I seems that an API is available but you need to pay for a subscription to use it. Not a very developer friendly system.

    Please open up the API (for free) to developers who own and want to use their device in their house(s).

    0
    Comment actions Permalink
  • Avatar
    Scottcunnyngham

    +1 on the free API.  I agree charging for services provided by Streamlabs that require the use of the API, such as downloading data is fair but if the end user has the wherewithal to access the API and manipulate the data without the services of StreamLabs that should remain free.  A good example of allowing users to access the API for development is Samsung SmartThings.  That practice has propelled that user base into the millions because of the huge amount of 3rd party development and support of that platform because of the free an open API.

     

    In today's environment a closed ecosystem is doomed to fail.  The Lowe's Iris platform is just one recent example.

    0
    Comment actions Permalink
  • Avatar
    Rachel S

    Hi,

     

    Thank you for your feedback. We plan to adjust our subscription details based on customer feedback and I have passed your concerns along to our team. Please let me know if you have any additional questions or concerns and feel free to reach out to us at support@streamlabswater.com.

     

    Thanks!

    0
    Comment actions Permalink
  • Avatar
    Scottcunnyngham

    Thanks for the positive reply Rachel.

    0
    Comment actions Permalink
  • Avatar
    Greg Kelley

    I agree that a paid subscription for advanced API use is justifiable for 'commercial' users (like landlords with multiple monitors) but there is enormous potential for sales to Smartthings users if there could be direct integration to simply set Home/Away (both ways - ST->SL and SL->ST) and have the Monitor throw a wet alert to ST so ST could close a valve. ST users do not require usage data (advanced API) just read/set Monitor status Home/Away/Wet/Dry. SmartLabs would benefit from increased sales to Smartthings users which would easily offset the lack of subscription fee income (these types of subscription-based business models have mostly failed in the past).

    0
    Comment actions Permalink

Please sign in to leave a comment.