Skip to content
Free planNo credit card requiredStart writing
AI for Research home
AI for Research home
Dashboard
Sign inGet started

Search 250 million research papers

Read the abstract, see who wrote it and who cites it, and get the citation in APA, MLA, Chicago or Harvard.

About 10,000 papers for “Application programming interface”

Nonlinear dispersion with the MODFLOW application programming interface

Pérez-Illanes, Rodrigo, Saaltink, Maarten W., Fernàndez-Garcia, Daniel · Zenodo (CERN European Organization for Nuclear Research) · 2024

Python routines based on FloPy for the simulation of solute transport problems with nonlinear dispersion, using the MODFLOW application programming interface.

Cited by 0Open access

Application Programming Interface-Digital Strategy for Core Banking

Arindam Roy · International Journal of Science and Research (IJSR) · 2024

Once regarded as a technical interface, the humble API is now praised as a strategic business asset that must be taken seriously.Around the world, banks are awakening to the transformational potential of APIs as the core building block of open banking. Here we consider APIs in the context of channel development and facilitating an "opti-channel" customer experience. By developing and selling access to new API products, banks are able to create additional direct revenue streams. These premium APIs can also be used as up-sells or cross-sells for other banking products (such as certain corporate accounts). APIs empower banks to deliver products and services in context when customers need them. As well as integrating bank products into third-party apps and services, APIs allow banks to disaggregate the banking value chain. This work provides a brief window into how API driven architecture is driving the digital transformation for banks.

Cited by 0Open access

DESIGNING OF ROBOT WORKSPACE BY APPLICATION PROGRAMMING INTERFACE

Miran Brezocnik, Simon Brezovnik, Simon Klancnik et al. · 2014

In this paper, we propose an application programming interface (API) for designing of a robot workspace. The interface is realized inside a SolidWorks computer aided design environment. Via API, the builder of the robot system can check if: a) the current robot mechanism can perform the desired work movements, b) the robot can avoid singularity, and c) the points of the robot trajectory are within the robot workspace. With the proposed approach, a more successful designing of robotic cells is assured. Keyworks: Robotics, SolidWorks, API interface, Workspace 1.

Cited by 0

Development of a Flutter Mobile Application Using Spotify’s Application Programming Interface

Ala-aho, Joel, Karjalainen, Ossi · Theseus (Ammattikorkeakoulujen) · 2022

This thesis followed the development process of a cross-platform mobile application in
\nthe form of personal weekly video diary entries. Each entry describes the weekly goals,
\nfinished tasks, current problems and following week’s plans.
\n
\nThe main aim of the thesis was to develop a music application for mobile devices that
\nutilizes Spotify’s application programming interface and enhances existing features in
\nSpotify’s own mobile application. The secondary aim for the thesis was to improve skills
\nin mobile application development.
\n
\nThe user interface of the application was designed using Adobe XD. The Flutter framework was used to develop the front-end for the application. Authentication and data were
\nhandled by Spotify’s Web API. Google Firebase’s Cloud Firestore was used for a temporary storage.
\n
\nThe results for the project were successful. The application was able to meet the required
\nspecifications. Development is still needed to apply for Spotify’s release license. The authors continue developing the application because they want the application to end up in
\nboth Google’s Play Store and Apple’s App store.

Cited by 0Open access

Direct search optimization application programming interface with remote access

Pedro Mestre, João Matias, Aldina Correia et al. · Scientific Repository of the Polytechnic Institute of Porto (The Polytechnic Institute of Porto) · 2022

Search Optimization methods are needed to solve optimization problems where the objective function and/or constraints functions might be non differentiable, non convex or might not be possible to determine its analytical expressions either due to its complexity or its cost (monetary, computational, time,...). Many optimization problems in engineering and other fields have these characteristics, because functions values can result from experimental or simulation processes, can be modelled by functions with complex expressions or by noise functions and it is impossible or very difficult to calculate their derivatives. Direct Search Optimization methods only use function values and do not need any derivatives or approximations of them. In this work we present a Java API that including several methods and algorithms, that do not use derivatives, to solve constrained and unconstrained optimization problems. Traditional API access, by installing it on the developer and/or user computer, and remote API access to it, using Web Services, are also presented. Remote access to the API has the advantage of always allow the access to the latest version of the API. For users that simply want to have a tool to solve Nonlinear Optimization Problems and do not want to integrate these methods in applications, also two applications were developed. One is a standalone Java application and the other a Web-based application, both using the developed API.

Cited by 9Open access

BrAPI - an Application Programming Interface for Plant Breeding Applications.

Abbeloos, Rafael, Backlund, Jan Erik, Basterrechea Salido, Martin et al. · Prodinra (INRA Bordeaux-Aquitaine) · 2019

Motivation[br/]\nModern genomic breeding methods rely heavily on very large amounts of phenotyping and genotyping data, presenting new challenges in effective data management and integration. Recently, the size and complexity of datasets have increased significantly, with the result that data is often stored on multiple systems. As analyses of interest increasingly require aggregation of datasets from diverse sources, data exchange between disparate systems becomes a challenge.[br/]\nResults[br/]\nTo facilitate interoperability among breeding applications, we present the public plant Breeding Application Programming Interface (BrAPI). BrAPI is a standardized web service Application Programming Interface (API) specification. The development of BrAPI is a collaborative, community-based initiative involving a growing global community of over a hundred participants representing several dozen institutions and companies. Development of such a standard is recognized as critical to a number of important large breeding system initiatives as a foundational technology. Â The focus of the first version of the API is on providing services for connecting systems and retrieving basic breeding data including germplasm, study, observation, and marker data. A number of BrAPI-enabled applications, termed BrAPPs, have been written, that take advantage of the emerging support of BrAPI by many databases.[br/]\nAvailability and Implementation[br/]\nMore information on BrAPI, including links to the specification, test suites, BrAPPs, and sample implementations is available at https://brapi.org/. The BrAPI specification and the developer tools are provided as free and open source.

Cited by 1Open access

Snapshots of interfaces using S3DB's API (Application Programming Interface).

Helena F. Deus (376964), Romesh Stanislaus (2716), Diogo F. Veiga (109911) et al. · Figshare · 2015

<p>These applications exemplify why the semantic web designs can be particularly effective at enabling generic tools to assist users in exploring data documenting very specific and very complex relationships. Snapshot A was taken from S3DB's web interface, which is included in the downloadable package<a href="http://www.plosone.org/article/info:doi/10.1371/journal.pone.0002946#pone.0002946-s3db1" target="_blank">[25]</a>. This interface was developed to assist in managing the database model and, therefore, is centered on the visualization and manipulation of the domain of discourse, its <i>Collections of Items</i> and <i>Rules</i> defining the documentation of their relations. The application depicted on snapshots B–D describe a document management tool S3DBdoc, freely available as a Bioinformatics Station module (see <a href="http://www.plosone.org/article/info:doi/10.1371/journal.pone.0002946#pone-0002946-g006" target="_blank">Figure 6</a>). The navigation is performed starting from the Project (C), then to the <i>Collection</i> (B) and finally to the editing of the <i>Statements</i> about an <i>Item</i> (D). The snapshot B illustrates an intermediate step in the navigation where the list of <i>Items</i> (in this case samples assayed by tissue arrays, for which there is clinical information about the donor) is being trimmed according to the properties of a distant entity, Age at Diagnosis, which is a property of the Clinical Information <i>Collection</i> associated with the sample that originated the array results. This interaction would have been difficult and computationally intensive to manage using a relational architecture. The RDF formatted query result produced by the API was also visualized using a commercial tool, Sentient Knowledge Explorer (IO-Informatics Inc), shown in snapshot E, and by Welkin, developed by the digital inter-operability SIMILE project at the Massachusetts Institute of Technology. See text for discussion of graphic representations by these tools. To protect patient confidentiality some values in snapshots B and D are scrambled and numeric sample and patient identifiers elsewhere are altered.</p>

Cited by 0Open access

Real-Time Cryptocurrency Calculator using an Application Programming Interface

S Imran Hussain, Vigneshwaran Ravichandran, K R Sabarisrinivas et al. · 2023

As the world transitions from cash payment mode to e-pay mode there is a huge difference in the currency values of different countries. Payments differ as the value of the currency changes in each country to solve this issue cryptocurrencies are introduced because each crypto has its own margin and market capacity, and the value of each cryptocurrencies are going to be the same in all country with respect to time. The cryptocurrency uses blockchain technology that keeps a continually expanding collection of ordered entries, called blocks, in a distributed database. Cryptography is used to join these chunks. A timestamp, transaction information, and a cryptographic hash of the preceding block are included in each block. The challenge encountered the existing system was there is no converter to see the change in value with the current currency value to overcome this issue real-time cryptocurrency converter is introduced in addition to the existing system. The system uses an Application Programming Interface (API) call made by the user instructs the programmer to do an action, after which the application makes an API request to the web server. There are many applications to exchange the currency and store it as assert but there is no application to show the conversion value of the real-time currency to cryptocurrency. In this cryptocurrency converter app, users are the option to choose the type of conversion they need, i.e, “this” crypto “to” “this” crypto so that the desired value of the crypto value can be obtained.

Cited by 0

Interface and application of constraint programming for musical composition

Zoetardt, Geoffroy · Digital Access to Libraries (Université catholique de Louvain (UCL), l'Université de Namur (UNamur) and the Université Saint-Louis (USL-B)) · 2016

This master's thesis aims to interface and apply the constraint programming to a software of musical composition: OpenMusic. It interfaces a constraint programming system Gecode to the language Lisp and develops a user's interface for this system into the musical software OpenMusic.

Cited by 0Open access

A Unified Application Programming Interface for Bundle Protocol Applications

Lanzoni, Silvia · AMS Degree Thesis (University of Bologna) · 2022

Next space missions should rely on the DTN architecture and its associated Bundle Protocol (BP) to cope with the challenges faced by interplanetary links, such as long delays and disruption. This has led to new BP implementations or new releases, incorporating version 7, recently standardized by IETF. Although positive per se, this has exacerbated an already existing fragmentation problem, as every implementation has its own API and its own set of bundle options supported, which is a significant obstacle to the development of third party applications.
\nTo alleviate this problem, a new “abstracted” API for bundle protocol applications, called Unified API, has been developed during this thesis, and it is presented here.
\nThe Unified API is a complete refactoring of the old “Abstraction Layer”. As the predecessor it aims to decouple a DTN application from the BP implementations, with great advantages in terms of portability, maintenance and interoperability. However, the Unified API is more ambitious and it has the goal to present also a new API, now much closer to the familiar UDP socket and, more generally, to facilitate the development of new DTN applications as much as possible.
\nTo obtain this, the whole structure has been organized in three layers, of which only the top one is seen by applications. This layer consists of four blocks, of which the most important is the “Socket” block. The other blocks provide the programmer with high-level tools to create and modify a bundle, to parse the input string, to implement conditional prints etc.
\nThe Unified API is compatible with most BP implementations (DTN2/DTNME, ION, IBR-DTN, µD3TN). As them, it is released as free software and it is going to replace its predecessors in the next release of the DTNsuite, the Unibo collection of DTN applications included in ION, the DTN implementation by NASA JPL.
\nThe hope is that the Unified API will encourage third-party programmers, thus contributing to the success of DTN networking.

Cited by 1