developer.risevision.comDeprecation Notice - Developer API – Rise Vision Digital Signage Help Center

risevision.comApp LoginHelp Center Community Contact Support Webinars Training Creative Services Sales Store Developer DocumentationSubmit a requestSign inAccess the Rise Vision App Sign Up Free Sign In Rise Vision Digital Signage Help Center Community Announcements Deprecation Notice - Developer API Follow Ezequiel Conte September 04, 2018 17:06 In order for us to innovate with new features and improve existing features that our users value the most, we are constantly making changes to our product. Given the fast pace of improvements, our Developer API & supporting documentation became inaccurate and provided incomplete functionality. In addition, its low adoption made it hard to justify the effort required to keep it up-to-date. Due to the above, we have decided to discontinue the Developer API. As of February 28, 2019, the Developer API ( https://developer.risevision.com ) will be closed and you will no longer be able to manage your API credentials. You can continue to use the API beyond this date, but please note that requests may eventually fail and we will not be able to provide support for issues related to the API. We appreciate your commitment to Rise Vision and your understanding. Thanks! 0 Facebook Twitter LinkedIn 9 Comments 9 comments Sort by Date Votes Jeff Siler September 17, 2018 19:27 We have been trying to develop a white label, using the API tools (I hired a college student computer science guy). We’ve got something pretty close to working for users to see our branded interface. I can manage displays and add a sub company and user in my RV account, and they will show up in our white label branded interface. Will anything we’ve done so far for my branded interface continue to work beyond the 2/28/19 date? Here’s our interface dbb.csramultimedia.com 0 Comment actions Permalink Ezequiel Conte September 18, 2018 17:24 Edited Hi Jeff, After 2/28/19, requests to the API will continue to work so your interface should continue to work without problems. But keep in mind that as stated in the announcement, Rise will no longer provide support and the requests may eventually fail at some point in the future. Thanks! 0 Comment actions Permalink Matt Schmandt February 28, 2019 17:14 We were just automating our presentations via the API and now its going to be killed off. Perfect. Do you have any plans for allowing customers to programmatically control their displays and presentations? 0 Comment actions Permalink Ezequiel Conte February 28, 2019 22:34 Hi Matt, Unfortunately, for the reasons mentioned above, we couldn’t justify the effort to maintain the Developer API. We don’t have plans to provide a replacement for it but the API will continue to work for now, although Rise will no longer provide support. Thanks 0 Comment actions Permalink ZS Support March 04, 2019 08:45 Hi, Just came across this disappointing post and I’m trying to understand the scope/effect. Does this announcement also mean that developing custom widgets will no longer be supported? We chose for RiseVision among other reasons because we were attracted by the Open Source model and option to create our own widgets. We plan to start working on the first one in the coming weeks so I’m really hoping that we can still do that. Unfortunately, I cannot find the documentation anymore (I suspect it was part of developer.risevision.com) Kindly clarify. If you’re making it impossible for us to integrate ourselves, also elaborate on your plans to support our specific integrations. Thanks 0 Comment actions Permalink Wendi Borden March 04, 2019 15:51 Goodness I hope not! Custom widgets are a huge thing for us and we have several customers still using them. As far as my understanding though, they are fine. Widgets are a separate ballgame from the API. The API allowed you to speak to RiseVision servers and make edits without logging into the site.. or see site status, pull information, etc. A widget is just some HTML and Javascript basically that shows up in a placeholder in your Presentation. There’s a post on the forum still for a "Hello World" widget that can get you started: https://www.risevision.com/blog/learn-how-to-build-a-widget-for-your-digital-signage Specifically, you’re really just interested in hosting and modifying the "src" folder from this repo: https://github.com/tantangula/rise-widget-hello-world Hopefully someone official will chime in though to ease the fear here. I’m still very sad the API is leaving.. we’re floating on it for now while we migrate away. We tried since 2015 to use Rise Vision but end up getting blocked at every turn :/ We successfully had over 200 signs on it though and it has been a pretty solid solution. 0 Comment actions Permalink Shea Darlison March 06, 2019 11:51 Hi all, I’m the Product Manager for the Content Team at Rise Vision, we’re responsible for the Widgets/Templates. I’d like to address your questions and concerns. Developer.risevision.com is deprecated and we will not be making the Widget documentation available again. We no longer recommend building Custom Widgets. If you have a custom digital signage application you want to build we recommend you build it as a web application and display is using the Web Page Widget or the Schedule by URL feature. Existing Custom Widgets will continue to work and as of now we do not have plans to remove the ability to add a Custom Widget to your Presentation. If we’re going to make changes that will prevent Custom Widgets from working or being added to a Presentation we will provide the community with notice. Let me know if you have any questions. Thanks 0 Comment actions Permalink ZS Support March 18, 2019 18:24 Hi Shea, Thanks for the clarification. Unfortunately my guess was right, and I’m still a bit in shock that a platform that till date has prided itself as open source would shut down the developers’ APIs. You suggested using the Web Page Widget but as you well know that widget does not support displaying authenticated content which makes it useless in many realistic use cases (which sane company will want to expose critical data via an unauthenticated means for the sake of digital signage?). While building our own web applications to bridge the gap is definitely an option, it doesn’t sound efficient and defeats the notion of a platform that’s OSS-oriented. it would make more sense to me that RiseVision facilitates this process either by allowing us to keep building custom applications and/or by extending/building a widget that supports modern authentication options. Postman is a good source of inspiration as per authentication options to support. Funny enough, my team was gearing up to tackle this challenge since the data we need to show may not be exposed without proper authentication. And we were considering making an open source generic widget that allows seamless authentication and displaying content. We had other interesting ideas like supporting mapping of raw JSON/XML data to placeholders... Honestly, this announcements feels like the beginning of the end of RiseVision as an open source platform and that’s really sad. I kindly invite you to consider the suggestions above and more importantly reconsider your decision. There must be other ways to spur the community on without shutting down the API. I can live with a paid API model if that helps with "keeping the lights on" but completely shutting it down? I’m still mildly in shock. In the meantime, we’ll see how far we get with what’s still available and perhaps have to look at alternatives (I hope not) :( Thanks for taking the time to read my ranting. 1 Comment actions Permalink Shea Darlison March 18, 2019 20:00 Thank you for the feedback. We’re continuously evaluating our strategy and will keep your comments in mind, but to be candid, I do not expect this decision to change soon. We fully respect your decision should to you decide to move to an alternate solution. Let me know if you have any other questions....