Of the many APIs we published this week, nine were highlighted on the blog by our team of writers. In this post, we’ll shine a spotlight on those nine, which included the Liquid Helium APIs. Stremor, the heuristics startup behind the APIs, aims to create a summarization framework for long form content. By applying language indicators such as cause, conclusion, relevance, and emotion, Liquid Helium can make accurate decisions about decreasing form length. To learn more about the Liquid Helium API visit the Liquid Helium site as well as the Liquid Helium API blog post.
The sharing of thousands of online images is a big part of daily social media interaction. Even with the accompanying comments enhanced by expressive punctuation or clever emoticons, however, nothing beats an actual spoken response for an accurate representation of how a person has really responded to an image or what they really think about that image. SayRoom makes this possible by allowing users to actually voice and share their recorded reactions. The service also provides the SayRoom API that allows developers to access these audio messages created by users.
Chrome Intersection Observers
||The Chrome Intersection Observers API allows developers to determine when an element in their DOM is visible to the end user. If an element is only partially visible, the API can determine what...||Viewer||06.15.2016|
||The Crisp Platform API is a security and content moderation solution of web content shared through social media channels and applications. The API allows users to detect and weed out security risks...||Social||06.15.2016|
||Apizee is a platform that integrates WebRTC technology, and adds real-time text, audio, and video capabilities to third party applications. This platform features visual collaboration, plugin-free...||WebRTC||06.07.2016|
||The Apizee ApiRTC API is a platform that integrates WebRTC technology, and adds real-time text, audio, and video capabilities to third party applications. This platform features visual colaboration,...||WebRTC||06.06.2016|
Web Speech Specification