About: Open API is a research topic. Over the lifetime, 442 publications have been published within this topic receiving 2904 citations. The topic is also known as: public API.
TL;DR: This work examines Android application interaction and identifies security risks in application components and provides a tool, ComDroid, that detects application communication vulnerabilities and found 34 exploitable vulnerabilities.
Abstract: Modern smartphone operating systems support the development of third-party applications with open system APIs. In addition to an open API, the Android operating system also provides a rich inter-application message passing system. This encourages inter-application collaboration and reduces developer burden by facilitating component reuse. Unfortunately, message passing is also an application attack surface. The content of messages can be sniffed, modified, stolen, or replaced, which can compromise user privacy. Also, a malicious application can inject forged or otherwise malicious messages, which can lead to breaches of user data and violate application security policies.We examine Android application interaction and identify security risks in application components. We provide a tool, ComDroid, that detects application communication vulnerabilities. ComDroid can be used by developers to analyze their own applications before release, by application reviewers to analyze applications in the Android Market, and by end users. We analyzed 20 applications with the help of ComDroid and found 34 exploitable vulnerabilities; 12 of the 20 applications have at least one vulnerability.
TL;DR: This project work deals with The IoT lsquoThingspeakrsquo web service which is a generous open API service that act as a host for the variety of sensors to monitor the sensed data at cloud level and composite a special feature of porting the sensedData to the MATLAB R2016a using a channel ID and read API key.
Abstract: As the expeditious of Internet of Things (IoT) is emerging and is accustom for remote monitoring of the surrounding parameters and other stuffs with the use of sensors that acquaint for wireless sensing of real time data and transfer them into the desired form and help to forward the sensed data across the network cloud via lsquoInternet Connectionrsquo. Here the project work deals with The IoT lsquoThingspeakrsquo web service which is a generous open API service that act as a host for the variety of sensors to monitor the sensed data at cloud level and composite a special feature of porting the sensed data to the MATLAB R2016a using a channel ID and read API key that is assigned by services and able to track data value at picky sample at particular intervals. This project also uses an Arduino UNO board, ESP8266 Wi-Fi Module that helps to process and transfer the sensed data to the Thingspeak Cloud.
TL;DR: In this article, a voice-based command-driven computer implemented method and programmed apparatus that allows a user to easily add any open API communication product they choose to one interface is presented.
Abstract: The present invention generally relates to a voice-based command driven computer implemented method and programmed apparatus that allows a user to easily add any open API communication product they choose to one interface. The computer implemented method filters all electronic communications selected by the user through a common source, such as the user's cell phone or computer. Each time an electronic communication is received, no matter through what program or application, the computer implemented method operates to communicate to the user that the electronic communication has been received and provides the user with the option of listening to and responding to the electronic communication, if appropriate. The user responds to the electronic communication through voice-based communication rather than physical interaction with the common source. The user may additionally initiate electronic communication through voice-based communication.
TL;DR: In this article, a method and system for an open API dashboard system for monitoring and managing one or more developer programmed applications configured to use services provided by a service owner is provided.
Abstract: A method and system for an open API dashboard system for monitoring and managing one or more developer programmed applications configured to use one or more services provided by a service owner are provided. The system includes an application area associated with a corresponding programmed application, each application area including a call metrics group configured to display summarized metrics, a services used group configured to display a listing of each service called by the programmed application and metrics associated with each service, and a key management group configured to prompt a developer of the programmed application to request or revoke a key, wherein the key includes a developer identification, a programmed application identification, and signed certificates relating to services used by the programmed application. The system also includes a side bar area configured to prompt a developer to request information or help relating to the application area.
TL;DR: This paper proposes an approach to generate specification-based test cases for REST APIs to make sure that such APIs meet the requirements defined in their specifications, and particularly the OpenAPI one.
Abstract: The REpresentation State Transfer (REST) has gained momentum as the preferred technique to design Web APIs. REST allows building loosely coupled systems by relying on HTTP and the Web-friendly format JSON. However, REST is not backed by any standard or specification to describe how to create/consume REST APIs, thus creating new challenges for their integration, testing and verification. To face this situation, several specification formats have been proposed (e.g., OpenAPI, RAML, and API Blueprint), which can help automate tasks in REST API development (e.g., testing) and consumption (e.g., SDKs generation). In this paper we focus on automated REST API testing relying on API specifications, and particularly the OpenAPI one. We propose an approach to generate specification-based test cases for REST APIs to make sure that such APIs meet the requirements defined in their specifications. We provide a proof-of-concept tool implementing our approach, which we have validated with 91 OpenAPI definitions. Our experiments show that the generated test cases cover on average 76.5% of the elements included in the OpenAPI definitions. Furthermore, our experiments also reveal that 40% of the tested APIs fail.