Development Of Application Programming Interface Research Articles

Exploring and evaluating the development of an open application programming interface (Open API) architecture for the fintech services ecosystem

PurposeThe Open API (application programming interface) architecture will play an important role in promoting future FinTech service applications; however, it involves user data, and the current specialization and progression are less visible. Therefore, an evaluation framework for Open API development in the FinTech service ecosystem is constructed in this study.Design/methodology/approachThis study preliminarily selects the four most important key objects and factors of this ecosystem and conducts expert interviews to revise the evaluation framework. Then, this study uses the fuzzy analytic hierarchy process (FAHP) to evaluate the objects and their factor weights and finally uses the FAHP analysis results to further apply the evaluation based on distance from average solution (EDAS) approach to explore the strategy optimization scenarios.FindingsAccording to the analysis results, the co-creation object and productivity object are the two most significant objects, with weights of 0.275 and 0.272, respectively. The analysis shows that FinTech-related companies expect to increase productivity through co-creation. Finally, the results also indicate that mobile payment is the best Open API application scenario in the FinTech service ecosystem, followed by online banking. These results illustrate strategic and management implications.Originality/valueThis study screens key evaluation criteria with a literature review and expert questionnaire interviews to process quantitative research. It can determine the weights of objectives and criteria to clarify the strength of influence between the objectives and criteria. Next, this study measures the probable performance of Open API applied in various FinTech service ecosystem scenarios.

An institutional perspective on application programming interface development and integration

PurposeDigital platforms increase their function and scope by leveraging boundary resources and complementary add-on products from third-party developers to interact with external entities and producers. Application Programming Interfaces (APIs) are essential boundary resources developers use to connect applications, systems and platforms. This notwithstanding, previous API studies tend to focus more on the technical dimensions, with little on the social and cultural contexts underpinning API innovations. This study relies on the new (neo) institutional theory (focusing on regulative, normative and cultural-cognitive pillars) as an analytical lens to understand the institutional forces that affect API integration among digital firms.Design/methodology/approachThe study adopts a qualitative case study methodology and relies on phone calls and a semi-structured in-depth interview approach of a Ghanaian digital music platform to uncover the institutional forces affecting API integration.FindingsThe findings reveal that regulative institutions such as excessive tax regimes mostly constrained API development and integration initiatives. However, other regulative institutions like the government digitalization agenda enabled API integration. Normative institutions, such as the growing use of e-payment options, enabled API integration in digital music platforms. Cultural-cognitive institutions like employee ego constrained the API integration process in music digital platforms.Originality/valueThis study primarily contributes to deepening understanding of the relevant literature by exploring the institutional forces that affect API integration among digital firms in a developing economy. The study also uncovered a new form of an institution known as motivational institution as an enabler for API development and integration in digital music platforms.

Design Automation for IC Engine Cooling System using Application Programming Interface

These In recent years, the intense competition in development of new products followed by their rapid prototyping has given rise to an intense competition in the market. In order to automate the design, development of Application Programming Interface (API) is most commonly followed method. The presented work showcases an attempt to develop an API for calculation of area of Heat Exchanger required for an IC Engine. The sAPI has been developed using two commonly used coding languages – HTML (Hypertext Markup Language) and Java script. The HTML along with the integration of CSS is used to develop the user interface and the mathematical formulae have been formatted into the Java script. The API is focused towards understanding the combined effect of various parameters in a heat transfer system.

API Development Teaching- Learning Platform

Abstract: API (Application Programming Interface) is a sequence of commands, rules, or regulations that enables a software or app to leverage attributes from another application, system, or gadget to improve its own services. In a nutshell, it's a feature that allows apps to connect with one another. The IT industry has a high demand for REST API Development, hence this article provides an interactive teaching and learning platform for REST API Development. Using the LBD (Learning By Doing) concept, the suggested platform seeks to assist users in learning REST API Development. This tool would assist users in learning to design their own APIs by requiring them to practise (either through coding or MCQs). The platform would be based on selfevaluation and reflection models of self-regulated learning, allowing users to learn more effectively. The platform would also try to provide some scaffolding for users that fail test cases, such as assistance in debugging and why they might be failing the test cases. Keywords: REST-API, Teaching Learning Platform, Self-Regulated Learning(SRL), Human Computer Interaction(HCI), Dashboard, Learning by doing(LBD)

Evaluating GraphQL and REST API Services Performance in a Massive and Intensive Accessible Information System

Currently, most middleware application developers have two choices when designing or implementing Application Programming Interface (API) services; i.e., they can either stick with Representational State Transfer (REST) or explore the emerging GraphQL technology. Although REST is widely regarded as the standard method for API development, GraphQL is believed to be revolutionary in overcoming the main drawbacks of REST, especially data-fetching issues. Nevertheless, doubts still remain, as there are no investigations with convincing results in evaluating the performance of the two services. This paper proposes a new research methodology to evaluate the performance of REST and GraphQL API services with two main ideas as novelties. The first novel method is the evaluation of the two services is performed on the real ongoing operation of the management information system, where massive and intensive query transactions take place on a complex database with many relationships. The second is the fair and independent performance evaluation results obtained by distributing client requests and synchronizing the service responses on the two virtually separated parallel execution paths for each API service, respectively. The performance evaluation was investigated using basic measures of QoS (Quality of Services), i.e., response time, throughput, CPU load, and memory usage. We use the term efficiency in comparing the evaluation results to capture differences in their performance measures. The statistical hypothesis parameters test using the two-tails paired t-test, and boxplot visualization was also given to confirm the significance of the comparison results. The results showed REST is still faster up to 50.50% in response time and 37.16% for throughput, while GraphQL is very efficient in resource utilization, i.e., 37.26% for CPU load and 39.74% for memory utilization. Therefore, GraphQL is the right choice when data requirements change frequently, and resource utilization is the most important consideration. REST is used when some data are frequently accessed and called by multiple requests.

Development of application programming interface prototype for injection molding machines

This paper describes architecture and development of an open application programming interface (API) prototype for injection molding machines (IMMs), useable for sensor and machine/process data logging and setting necessary process parameter values. The API is based on PCMEF (presentation, control, domain and foundation) architectural framework and OSI 7 layer communication model. The interface allows to retrieve values of up to 97 machine and process parameters. It also includes a module for acquisition of data from additional sensors such as pressure and temperature sensors installed in the mold. Industrial Raspberry Pi (RevPi) is used to perform analog-to-digital signal conversion and makes sensors data accessible via the API. Logging of different parameters from the machine and from sensors is synchronized and sampling frequency can be adjusted if necessary. Depending on chosen frequency, the system can provide real-time or soft real-time communication. The interface allows to build a distributed computer-based system, which gives benefit over the use of a PLC system with respect to Industry 4.0 standards.

Application Programming Interface for Flood Forecasting from Geospatial Big Data and Crowdsourcing Data

Nowadays, natural disasters tend to increase and become more severe. They do affect life and belongings of great numbers of people. One kind of such disasters that hap-pen frequently almost every year is floods in all regions across the world. A prepara-tion measure to cope with upcoming floods is flood forecasting in each particular area in order to use acquired data for monitoring and warning to people and involved per-sons, resulting in the reduction of damage. With advanced computer technology and remote sensing technology, large amounts of applicable data from various sources are provided for flood forecasting. Current flood forecasting is done through computer processing by different techniques. The famous one is machine learning, of which the limitation is to acquire a large amount big data. The one currently used still requires manpower to download and record data, causing delays and failures in real-time flood forecasting. This research, therefore, proposed the development of an automatic big data downloading system from various sources through the development of applica-tion programming interface (API) for flood forecasting by machine learning. This research relied on 4 techniques, i.e., maximum likelihood classification (MLC), fuzzy logic, self-organization map (SOM), and artificial neural network with RBF Kernel. According to accuracy assessment of flood forecasting, the most accurate technique was MLC (99.2%), followed by fuzzy logic, SOM, and RBF (97.8%, 96.6%, and 83.3%), respectively.

Use of ESSENCE APIs to Support Flexible Analysis and Reporting

ObjectiveTo describe and provide examples of the Electronic Surveillance System for the Early Notification of Community-based Epidemics (ESSENCE) application programming interface (API) as a part of disease surveillance workflows.IntroductionThe ESSENCE application supports users’ interactive analysis of data by clicking through menus in a user interface (UI), and provides multiple types of user defined data visualization options, including various charts and graphs, tables of statistical alerts, table builder functionality, spatial mapping, and report generation. However, no UI supports all potential analysis and visualization requirements. Rapidly accessing data processed through ESSENCE using existing access control mechanisms, but de-coupled from the UI, supports innovative analyses, visualizations and reporting of these data using other tools.MethodsThe ESSENCE API gives users the ability to query ESSENCE data and functionality via a Representational State Transfer (REST) web API designed to use HTTPs protocol. As with logging into the ESSENCE application normally, use of the API also requires users to authenticate with their username and password by including it in the code. This makes programmatic interfaces with the application possible whereby a tool or program makes a request to the API endpoint and the API returns the result of the query in a structured form. The ESSENCE API is a collection of endpoints that return different sets of data, including ESSENCE time series graphs, time series data, data details data, aggregated data created using the table builder functionality, number of unique facilities or regions (i.e. counties) reporting for a query, and results from the detector algorithms and alert list. All of the query parameter information is stored in the API URL, which the user can create programmatically or by first creating their query from within ESSENCE, and then clicking the “API URL” to generate the necessary URL. API results are generally available in both json and csv formats.ResultsEpidemiologists in the CDC NSSP have developed R code that uses these APIs to create customized Rmarkdown reports and visualizations not possible within the ESSENCE application, as well as to automate extraction of data from ESSENCE to support routine reporting for other CDC program areas (e.g., influenza-like illness, and suspected opioid encounters). Anecdotally, some Sites utilize the API to populate publically facing dashboards with aggregated data from ESSENCE. Programmatic access to processed ESSENCE data via the APIs also supports easily sharable exploratory analysis and visualization that can serve as a sandbox for testing new methods for future inclusion within ESSENCE.ConclusionsThe development and use of the ESSENCE APIs in public health surveillance will support more efficient and timely access to machine-readable data de-coupled from point and click user interfaces, and has the potential to spur new and innovative ways of using data that has traditionally been less programmatically accessible to users. New tools and programs can leverage the data in web or mobile applications, traditional reports, and more easily integrate disparate data sources for comprehensive surveillance.

PERANCANGAN APPLICATION PROGRAMMING INTERFACE (API) BERBASIS WEB MENGGUNAKAN GAYA ARSITEKTUR REPRESENTATIONAL STATE TRANSFER (REST) UNTUK PENGEMBANGAN SISTEM INFORMASI ADMINISTRASI PASIEN KLINIK PERAWATAN KULIT

Application Programming Interface (API) is an interface built by system developer so some or entire functions of the system can programatically be accessed. Representational State Transfer (REST) is one of API development architectural style that uses Hypertext Transfer Protocol (HTTP) for data communication. This research implemented REST in developing API as the back-end of the skincare clinic patient information system. API was developed using Javascript Object Notation (JSON) as the standard format for data communication and JSON Web Token (JWT) as user authentication code. This research indicates that the development of API successfully performed on the patient administration of skin care clinic and implementation of REST makes it easy to develop API structures. This research produced REST API-based back-end for the patient administration information system of skin care clinic. API was tested in three stages: JWT testing on multiple back-end servers, API testing with Equivalence Partitioning and system functional testing. Keywords : application programming interface (api), hypertext transfer protocol (http), javascript object notation (json), json web token (jwt), representational state transfer (rest).

Leveraging Web 2.0 technologies to add value to the IUPAC Solubility Data Series: development of a REST style website and application programming interface (API)

Abstract This paper details an approach to re-purposing scientific data as presented on a web page for the sole purpose of making the data more available for searching and integration into other websites. Data ‘scraping’ is used to extract metadata from a set of pages on the National Institute of Standards and Technology (NIST) website, clean, organize and store the metadata in a MySQL database. The metadata is then used to create a new website at the authors institution using the CakePHP framework to create a representational state transfer (REST) style application program interface (API). The processes used for website analysis, schema development, database construction, metadata scraping, REST API development, and remote data integration are discussed. Lessons learned and tips and tricks on how to get the most out of the process are also included.

공간정보 오픈플랫폼 설계를 위한 2D Web Mapping Open API 비교 연구

Google 지도는 AJAX(Asynchronous JavaScript and XML) 기술을 이용하여 Web-GIS의 반응 속도를 크게 변화시켰다. 또한 Google은 Open API(Application Programming Interface)인 Google Maps API를 공개하여 기존의 SDK(Software Development Kit)와 ASP(Application Service Provider)가 주도하던 지도 시장에 Open API라는 패러다임의 변화를 가져왔다. 이후, 많은 정부와 기업과 오픈소스 진영에서 비슷한 방식의 Open API를 내놓았으며 Web-GIS 시장을 키워왔다. 또한 HTML5 표준에 대한 최신 웹브라우저의 적극적인 표준 구현으로 인해 웹지도는 단순한 웹페이지가 아닌 하나의 웹어플리케이션으로 진화하여 속도와 성능향상을 이루었다. 하지만 많은 공간정보 2D Open API들이 나왔지만 국내의 API에 대한 현실적인 비교분석은 잘 이루어지지 않은 실정이다. 따라서 본 논문에서는 먼저 공간정보 2D Open API를 이루고 있는 구성요소들을 살펴보고, 각각의 API들이 어떠한 기능들을 얼마만큼 지원하는지를 살펴보고자 한다. 또한 각 API 별로 기능적인 특징과 서비스적인 특징들을 살펴보고 비교분석을 수행하고자 한다. 끝으로, 공간정보 2D Open API의 서비스 사례들을 살펴보고 앞으로의 발전 방향에 대해 제시하고자 한다. Google Maps have changed the response time of Web-GIS using AJAX technologies. In addition, Google released the Open API named Google Maps API(Application Programming Interface) and it lead to the big paradigm on the Open API, where the SDK(Software Development Kit) and ASP(Application Service Provider) had ruled at the related map market. In short, the Open API has been paradigm-shifting for the web mapping. After this, government, many companies and open source foundations have guided Web-GIS market's growth through releasing the relevant Open APIs. So many comparative analysis on web-mapping API carried out by many researches. However there were no researches that can be applied to our current domestic environments. This paper investigates components of web-mapping API. Then we compare how many components supported and enumerate features for each of those APIs. Finally this paper presents direction of future development of Web Mapping API.

Access to online archival catalogues via web APIs

This paper describes State Records New South Wales' Open Data Project and the development of a web API (Application Programming Interface) to the online catalogue, Archives Investigator. In the course of developing the web API, a new experimental user interface to the catalogue was also built. Key features of that new interface are described.

Modeling of the XOM/XMP application programming interface (API)

With the growing complexity of communication protocols, it is increasingly difficult for application developers to interface the applications to the communication stacks across a number of platforms. A common application program interface (API) is needed for the purpose. The API can effectively conceal the complexities of communication protocols and architecture, making it easier for application development. This article presents the modeling and development of a generic API, XOM and an application-specific API, XMP. XOM API provides a general-purpose data handling mechanism and XMP API provides service primitives to network management protocols. The development is based on object-oriented technology. The attractiveness of object-oriented implementation is its ability to provide encapsulation, reusability and extensibility in the software modules. The benefits and difficulties encountered during the implementation are to be discussed. The experience will be useful for API development.