Academic literature on the topic 'APIs REST'

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles

Select a source type:

Consult the lists of relevant articles, books, theses, conference reports, and other scholarly sources on the topic 'APIs REST.'

Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.

You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.

Journal articles on the topic "APIs REST"

1

Baniaș, Ovidiu, Diana Florea, Robert Gyalai, and Daniel-Ioan Curiac. "Automated Specification-Based Testing of REST APIs." Sensors 21, no. 16 (August 9, 2021): 5375. http://dx.doi.org/10.3390/s21165375.

Full text
Abstract:
Nowadays, REpresentational State Transfer Application Programming Interfaces (REST APIs) are widely used in web applications, hence a plethora of test cases are developed to validate the APIs calls. We propose a solution that automates the generation of test cases for REST APIs based on their specifications. In our approach, apart from the automatic generation of test cases, we provide an option for the user to influence the test case generation process. By adding user interaction, we aim to augment the automatic generation of APIs test cases with human testing expertise and specific context. We use the latest version of OpenAPI 3.x and a wide range of coverage metrics to analyze the functionality and performance of the generated test cases, and non-functional metrics to analyze the performance of the APIs. The experiments proved the effectiveness and practicability of our method.
APA, Harvard, Vancouver, ISO, and other styles
2

Jiang, Nan, and Yan Zhong Hu. "Cloud Computing Model and REST APIs Implementation." Advanced Materials Research 366 (October 2011): 416–20. http://dx.doi.org/10.4028/www.scientific.net/amr.366.416.

Full text
Abstract:
Cloud computing exposes software as a service, platform as a resource, and infrastructure as a service. The way of Web services work naturally makes it the system interface for software communication of a cloud computing architecture. And REST(REpresentational Status Transfer) philosophy is a better way to construct Web services since it is fundamental to the Web and can make full use of the features of the Web. We implement RESTful APIs for learning resource cloud, and the benefits of an Ajax(Asynchronous JavaScript and XML) Web service client to the REST APIs are discussed.
APA, Harvard, Vancouver, ISO, and other styles
3

Paredes-Valverde, Mario Andrés, Giner Alor-Hernández, Alejandro Rodr’guez-González, and Gandhi Hernández-Chan. "Developing Social Networks Mashups: An Overview of REST-Based APIs." Procedia Technology 3 (2012): 205–13. http://dx.doi.org/10.1016/j.protcy.2012.03.022.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Ferreira, Hiro Gabriel Cerqueira, Edna Dias Canedo, and Rafael Timóteo De Sousa Junior. "A ubiquitous communication architecture integrating transparent UPnP and REST APIs." International Journal of Embedded Systems 6, no. 2/3 (2014): 188. http://dx.doi.org/10.1504/ijes.2014.063816.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Mowla, Saleh, and Sucheta V. Kolekar. "Development and Integration of E-learning Services Using REST APIs." International Journal of Emerging Technologies in Learning (iJET) 15, no. 04 (February 26, 2020): 53. http://dx.doi.org/10.3991/ijet.v15i04.11687.

Full text
Abstract:
E-Learning systems have gained a lot of traction amongst students and academicians due to their flexible nature in terms of location independence, time, effort, cost and other resources. The rapidly changing nature of the education domain makes the design, development, testing, and maintenance of E-Learning systems complex and expensive. In order to adapt to the changing policies of educational institutes as well as improve the performance of students, the paper presents a Service-Oriented Architecture (SOA) approach to minimize the cost and time associated with the development of E-Learning systems. The paper illustrates the development of independent E-Learning web services and how they can be combined to implement the required policies of respective education institutes. The paper also presents a sample policy implemented using developed web services to achieve the required objectives.
APA, Harvard, Vancouver, ISO, and other styles
6

Paganelli, Federica, Terence Ambra, Alessandro Fantechi, and Dino Giuli. "Formalizing REST APIs for web-based communication and SIP interworking." Telecommunication Systems 66, no. 1 (January 27, 2017): 75–93. http://dx.doi.org/10.1007/s11235-016-0271-2.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Haupt, Florian, Frank Leymann, and Karolina Vukojevic-Haupt. "API governance support through the structural analysis of REST APIs." Computer Science - Research and Development 33, no. 3-4 (September 22, 2017): 291–303. http://dx.doi.org/10.1007/s00450-017-0384-1.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Katayama, T., M. Nakao, and T. Takagi. "TogoWS: integrated SOAP and REST APIs for interoperable bioinformatics Web services." Nucleic Acids Research 38, Web Server (May 14, 2010): W706—W711. http://dx.doi.org/10.1093/nar/gkq386.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Wang, Dong Jin, Mei Na Song, and Yan Li. "OneAPI Restful Services and Java Implementation." Advanced Materials Research 143-144 (October 2010): 1159–63. http://dx.doi.org/10.4028/www.scientific.net/amr.143-144.1159.

Full text
Abstract:
In the past several years, there have been dramatic changes on the Web services landscape.After the traditional XML-PC web service, a new style-Representati0nal State Transfer (REST) is applied to Web services. In addition, the telecom operators have provided different APIs. OneAPI standards have been proposed. This article mainly introduces OneAPI standards and REST architecture. Some OneAPI supplied by GSMA website to provide REST service. Sample program implements can get the user address though the OneAPI.
APA, Harvard, Vancouver, ISO, and other styles
10

Rantanen, Petri. "REST API example generation using Javadoc." Computer Science and Information Systems 14, no. 2 (2017): 447–66. http://dx.doi.org/10.2298/csis161022009r.

Full text
Abstract:
Formatting and editing documentation can be a tedious process regardless of how well your documentation templates are made. Especially, keeping the code examples up-to-date can be time-consuming and error-prone. The research presented in this article describes a Javadoc extension that can be used to produce example data in combination with automatically generated API method call examples, and explains how the APIs in our implementation are organized to further ease the automatic documentation process. The primary goal is to make generating method call examples for (RESTful) web services easier. The method has been used in the implementation of a media content analysis service, and the experiences, advantages of using the described approach are discussed in this article. The method allows easier validation and maintenance for the documentation of method usage examples with a downside of an increased workload in the implementation of software components required for the automatic documentation process.
APA, Harvard, Vancouver, ISO, and other styles
More sources

Dissertations / Theses on the topic "APIs REST"

1

Karlsson, Axel. "Automatic Test Generation of REST APIs." Thesis, Linköpings universitet, Institutionen för datavetenskap, 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-170878.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Ed-douibi, Hamza. "Model-driven round-trip engineering of REST APIs." Doctoral thesis, Universitat Oberta de Catalunya, 2019. http://hdl.handle.net/10803/667111.

Full text
Abstract:
Les API web s'han convertit cada vegada més en un actiu clau per a les empreses, que n'han promogut la implementació i la integració en les seves activitats quotidianes. A la pràctica, la majoria d'aquestes API web són "REST-like", que significa que s'adhereixen parcialment a l'estil arquitectònic conegut com transferència d'estat representacional ('representational state transfer', REST en anglés). De fet, REST és un paradigma de disseny i no proposa cap estàndard. Com a conseqüència, tant desenvolupar com consumir API REST són tasques difícils i costoses per als proveïdors i clients de l'API. L'objectiu d'aquesta tesi és facilitar el disseny, la implementació, la composició i el consum de les API REST, basant-se en tècniques d'enginyeria dirigida per models ('model-driven engineering', MDE en anglés). Aquesta tesi proposa les contribucions següents: EMF-REST, APIDiscoverer, APITester, APIGenerator, i APIComposer. Aquestes contribucions constitueixen un ecosistema que avança l'estat de la qüestió al camp de l'enginyeria de programari automàtica per al desenvolupament i el consum de les API REST.
Las API Web se han convertido en una pieza fundamental para un gran número de compañías, que han promovido su implementación e integración en las actividades cotidianas del negocio. En la práctica, estas API Web son "REST-like", lo que significa que se adhieren parcialmente al estilo arquitectónico conocido como transferencia de estado representacional ('representational state transfer', REST en inglés). De hecho, REST es un paradigma de diseño y no propone ningún estándar. Por ello, tanto el desarrollo como el consumo de API REST son tareas difíciles y que demandan mucho tiempo de los proveedores y los clientes de API. El objetivo de esta tesis es facilitar el diseño, la implementación, la composición y el consumo de API REST, apoyándose en el desarrollo de software dirigido por modelos (DSDM). Esta tesis propone las siguientes contribuciones: EMF-REST, APIDiscoverer, APITester, APIGenerator y APIComposer. Estas contribuciones constituyen un ecosistema que avanza el estado de la cuestión en el área de la ingeniería del software referida a la automatización de las tareas relacionadas con el desarrollo y consumo de API REST.
Web APIs have become an increasingly key asset for businesses, and their implementation and integration in companies' daily activities has thus been on the rise. In practice, most of these Web APIs are "REST-like", meaning that they adhere partially to the Representational State Transfer (REST) architectural style. In fact, REST is a design paradigm and does not propose any standard, so developing and consuming REST APIs end up being challenging and time-consuming tasks for API providers and clients. Therefore, the aim of this thesis is to facilitate the design, implementation, composition and consumption of REST APIs by relying on Model-Driven Engineering (MDE). Likewise, it offers the following contributions: EMF-REST, APIDiscoverer, APITester, APIGenerator and APIComposer. Together, these contributions make up an ecosystem which advances the state of the art of automated software engineering for REST APIs.
APA, Harvard, Vancouver, ISO, and other styles
3

OLSSON, ROBERT. "Applying REST principles on local client-side APIs." Thesis, KTH, Skolan för datavetenskap och kommunikation (CSC), 2014. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-153671.

Full text
Abstract:
Abstract In this thesis, the application of REST principles on local clientside APIs is explored. REST is a popular software architectural style designed with simplicity, scalability and generality in mind. The benefits and drawbacks of using REST over conventional styles of designing local APIs have been investigated, with a specific focus on libspotify. Libspotify is a C API that allows third-party developers to use Spotify’s music streaming service. A local REST API was implemented on top of the libspotify C API. Software metrics were applied to the APIs, showing that the implementation was less decoupled than the equivalent C API. The metric results and relevant previous studies were used to analyze REST in local APIs. The main benefit was found to be the decoupling, leading to better evolvabilityand maintainability of an API. The main drawback is the additional work needed to model a REST API, and to make it more user friendly. The conclusion is that libspotify can benefit from REST, but that it might require more work than designing a conventional local API.
Applicering av REST-princper på lokala API:er på klientsidan I det här examensarbetet utforskas användningen av REST principer på lokala API:er. REST är en populär arkitekturstil för att utveckla mjukvara, designad för att vara enkel, skalbar och generell. För- och nackdelar med att använda REST istället för konventionella stilar att utveckla API:er har utforskats, med fokus på libspotify. Libspotify är ett C-API som låter tredjepartsutvecklare använda Spotifys musikströmningstjänst. Ett lokalt REST-API implementerades ovanpå libspotifys C-API. Metoder för att mäta API:ernas egenskaper användes, som visade att det existerande API:t hade ett större beroende mellan mjukvarukomponenter än REST-API:t. Mätresultaten och tidigare relevanta studier användes för att analysera REST i lokala API:er. Den huvudsakliga fördelen visade sig vara det minskade beroendet mellan mjukvarukomponenter, vilket leder till att API:t blir lättare att utveckla och underhålla. Den största nackdelen är det extra arbete som krävs föratt dels modellera ett REST-API, och dels göra det mer användarvänligt. Slutsatsen är att libspotify kan dra nytta utav REST, men att det kan innebära mer arbete än att designa ett konventionellt lokalt API.
APA, Harvard, Vancouver, ISO, and other styles
4

Coquand, Marc. "Evaluating Functional Programming for Software Quality in REST APIs." Thesis, Umeå universitet, Institutionen för datavetenskap, 2019. http://urn.kb.se/resolve?urn=urn:nbn:se:umu:diva-163967.

Full text
Abstract:
Defects in Software engineering are a common occurrence. To mitigate defects the developers must create maintainable solutions and strive for good software quality. A maintainable solution is readable, extensible, not error-prone and testable. In order to make them so developers follow a guideline called SOLID principles. These principles are not enforced by the language but relies on the diligence of the developers, meaning there is nothing stopping them from writing unmaintainable code. This study translates these principles to Functional programming to investigate if Functional programming can be used to construct a library for servers that forces the developer to create correct code without incurring costs in maintenance and readability.
APA, Harvard, Vancouver, ISO, and other styles
5

Tatrous, Adell, and Rasmus Svensson. "Design Abstraction of IoT REST APIs : Defining Design Patterns." Thesis, Linnéuniversitetet, Institutionen för datavetenskap och medieteknik (DM), 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:lnu:diva-97138.

Full text
Abstract:
Smart devices (or things) in the realm of IoT (Internet of Things) talk to each other and transfer data over the Internet.IoT vendors provide APIs for their clients to send data to the gateways and application servers. However, there is a lack of guidelines on how a vendor would design its API and resource URIs (Uniform Resource Identifiers). A generic design solution –design patterns– would make the API design and development easier for the vendors. Design patterns are reusable solutions to recurring problems and provide improved reusability and understandability. Currently, there are no design patterns for URIs of IoT APIs that IoT vendors can use. In this paper, we analyzed more than 1,300 URIs from 13 IoT APIs including IBM Watson and Microsoft Azure, and proposed eight novel design patterns for URIs of IoT APIs. We analyzed one dataset divided into two subsets: (1) analysis set with 70% of all our URIs to define design patterns for URIs of IoT APIs and (2) validation set with the remaining 30% of the URIs to verify the prevalence of the defined design patterns. We could map 84% of our validation set to the defined design patterns, i.e., design patterns are prevalent in the IoT domain.
APA, Harvard, Vancouver, ISO, and other styles
6

Vosta, Diba. "Evaluation of the t-wise Approach for Testing REST APIs." Thesis, KTH, Skolan för elektroteknik och datavetenskap (EECS), 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-287383.

Full text
Abstract:
A combinatorial explosion can occur when all possible combinations of all input parameters of a system are tested. When the number of input parameters and their possible values increase, the number of tests needed to cover each new case increases exponentially. Combinatorial interaction testing (CIT) is a black-box testing technique used to avoid a combinatorial explosion. CIT finds errors that are triggered by the interactions between parameters. One of the so-called combination strategies that can be used for CIT is t-wise testing. T-wise testing requires at least one test case for each combination of any t parameter values where t is the chosen strength - the number of parameters amongst which the interactions are tested. In this report, CIT with t-wise testing is applied to the testing of REST APIs. The thesis examines how 1-wise, 2-wise and 3-wise interaction testing compare when it comes to detecting injected faults in the code of REST APIs. It also studies the effectiveness of the three t-wise combinations in terms of run-time. The questions were examined through three API endpoints where the 1-wise, 2-wise and 3-wise test suites were generated directly from their OpenAPI specification. These test suites were constructed with parameter values in accordance with boundary value analysis and equivalence class partitioning. To answer the questions of this study, mutation testing was used as a means of injecting faults into the system under test. The mutants were developed specifically for this study as the input validation of the affected APIs was done through code annotations of which there are not many established mutation operators. The results of this study show that 1-wise, 2-wise and 3-wise testing of REST APIs all detect the same injected faults when performing mutation testing on the test suites. Furthermore, it showed that the run-time of the test suites increases significantly as the strength of t-wise testing increases. However, these results are limited to this particular study and cannot be assumed to coincide with other REST APIs. To further strengthen this conclusion for the general case, possible future work is suggested.
En kombinatorisk explosion kan uppstå när all möjliga kombinationer av inputparametrar av ett system testas. Antal testfall som behövs för att täcka alla kombinationer av inputparametrar växer exponentiellt när antalet parametrar och dess möjliga värden ökar. För att undvika en kombinatorisk explosion används kombinatorisk interaktionstestning vilket är en typ av black box testning. Syftet med kombinatorisk interaktionstestning är att hitta de fel som uppstår på grund av interaktioner mellan parametrar. Kombinatorisk interaktionstestning har ett flertal så kallade kombinationsstrategier och den kombinationsstrategi som denna rapport använder är t-wise testning. Kravet med t-wise testning är att skapa åtminstone ett testfall för varje kombination av t parametervärden där t är styrkan mätt i antalet parametrar som interaktioner sinsemellan testas. Denna rapport evaluerar effekterna av t-wise testning som en testningsmetod för REST APIer. Uppsatsen jämför hur väl 1-wise, 2-wise och 3-wise interaktionstestning upptäcker injicerade fel i källkoden av ett REST API. Utöver det undersöks även hur effektiva testsekvenserna är med hänsyn till exekveringstiden. Dessa aspekter undersöktes med hjälp av tre API slutpunkter där testsekvenser för 1-wise, 2-wise och 3-wise skapades direkt utifrån deras OpenAPI specifikationer. Testsekvenskerna som skapades använde gränsvärdeanalys och ekvivalensklasspartitionering för att generera parametervärden. För att kunna besvara frågorna i uppsatsen användes mutationstestning för att injicera fel i källkoden. I det här fallet utvecklades mutanterna specifikt för studien eftersom APIernas inputvalidering bestod av valideringsregler vilka inte har fastställda mutationsoperatorer. Resultaten av studien visade att både 1-wise, 2-wise och 3-wise testning av REST APIer kunde identifiera samma injicerade fel. Därutöver förlängs exekveringstiden av en testsekvens markant när styrkan av t-wise testning ökar. Däremot är dessa resultat begränsade till just detta arbete och kan inte antas stämma för alla fall at t-wise testning av REST APIer. För att stärka slutsatsen av detta arbete och generalisera svaren på frågorna föreslås framtida arbeten som kan göras.
APA, Harvard, Vancouver, ISO, and other styles
7

Karlsson, Oliver. "A Performance comparison Between ASP.NET Core and Express.js for creating Web APIs." Thesis, Jönköping University, JTH, Avdelningen för datateknik och informatik, 2021. http://urn.kb.se/resolve?urn=urn:nbn:se:hj:diva-54286.

Full text
Abstract:
Modern web applications are growing in complexity and becoming more widely used. Using frameworks to build APIs is a popular way for both hobby developers and businesses to speed up development time and save costs. With this dependence on frameworks to be the foundation for potentially large applications comes the need to understand their performance qualities and which areas they are best suited for. This study compares the performance of the two similarly popular frameworks ASP.NET Core and Express.js, when used together with a MySQL Database to build Web APIs. This was done by building two different API implementations in each framework, one employing a RESTful approach and the other using the new querying language GraphQL. Experiments were run where the peak CPU usage, peak memory usage and response times were measured.The results of the experiments were that in a RESTful API, ASP.NET Core is faster at serving requests during lower loads whereas Express.js outperforms ASP.NET Core when faced with a higher amount of concurrent requests that fetch a lot of data. In a GraphQL API Express.js was able to perform similarly or better in all cases in terms of response times and resource usage compared to ASP.NET Core.
APA, Harvard, Vancouver, ISO, and other styles
8

Danielsson, Tina. "Portering från Google Apps REST API till Microsoft Office 365 REST API." Thesis, Linköpings universitet, Artificiell intelligens och integrerad datorsystem, 2015. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-119076.

Full text
Abstract:
Stress på arbetsplatsen relaterat till många inkommande och utgående kommunikationskanaler är ett reellt problem. Applikationer som samlar alla kanaler i samma verktyg kan hjälpa till på det här området. För att förenkla vid utveckling av en sådan applikation kan ett modulärt system skapas, där varje modul ser liknande ut och enkelt kan kopplas in i en huvudapplikation. Den här studien undersöker de problem som kan uppstå när flera tjänster ska integreras, mer specifikt genom att titta på hur en befintlig modul för e-post via Google Apps kan porteras för att stödja e-post via Microsoft Office 365. Arbetet har skett enligt metoder för testdriven portering och varje steg i porteringen har dokumenterats noggrant. Ett antal problemområden har identifierats och möjliga lösningar föreslås. Utfrån de problem som uppstått dras slutsatsen att de är av en sådan karaktär att de inte utgör något hinder för en portering.
APA, Harvard, Vancouver, ISO, and other styles
9

Segedy, Patrik. "Fuzz testování REST API." Master's thesis, Vysoké učení technické v Brně. Fakulta informačních technologií, 2020. http://www.nusl.cz/ntk/nusl-417280.

Full text
Abstract:
Táto práca sa zaoberá fuzz testovaním REST API. Po prezentovaní prehľadu techník používaných pri fuzz testovaní a posúdení aktuálnych nástrojov a výskumu zameraného na REST API fuzz testovanie, sme pristúpili k návrhu a implementácii nášho REST API fuzzeru. Základom nášho riešenia je odvodzovanie závislostí z OpenAPI formátu popisu REST API, umožňujúce stavové testovanie aplikácie. Náš fuzzer minimalizuje počet po sebe nasledujúcich 404 odpovedí od aplikácie a testuje aplikáciu viac do hĺbky. Problém prehľadávania dostupných stavov aplikácie je riešený pomocou usporiadania závislostí tak, aby sa maximalizovala pravdepodobnosť získania potrebných vstupných dát pre povinné parametre, v kombinácii s rozhodovaním, ktoré povinné parametre môžu využívať aj náhodne generované hodnoty. Implementácia je rozšírením Schemathesis projektu, ktorý generuje vstupy za pomoci Hypothesis knižnice. Implementovaný fuzzer je použitý na testovanie Red Hat Insights aplikácie, kde našiel 32 chýb, z čoho jednu chybu je možné reprodukovať len za pomoci stavového testovania.
APA, Harvard, Vancouver, ISO, and other styles
10

Koudelka, Jakub. "Metodika návrhu REST rozhraní aplikací." Master's thesis, Vysoká škola ekonomická v Praze, 2011. http://www.nusl.cz/ntk/nusl-150021.

Full text
Abstract:
This work deals with an analysis and design of application programming interface (API) within the architectural style known as REST (Representational State Transfer). Beginning of this thesis covers basic introduction of HTTP protocol and REST fundamentals, followed by analysis and solution proposals of common situations that can occur in API. Sample application was implemented by following these proposals.
APA, Harvard, Vancouver, ISO, and other styles
More sources

Books on the topic "APIs REST"

1

Relan, Kunal. Building REST APIs with Flask. Berkeley, CA: Apress, 2019. http://dx.doi.org/10.1007/978-1-4842-5022-8.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

REST API design rulebook. Sebastopol, CA: O'Reilly Media, 2011.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
3

Doglio, Fernando. REST API Development with Node.js. Berkeley, CA: Apress, 2018. http://dx.doi.org/10.1007/978-1-4842-3715-1.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Doglio, Fernando. Pro REST API Development with Node.js. Berkeley, CA: Apress, 2015. http://dx.doi.org/10.1007/978-1-4842-0917-2.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Yudin, Art. Building Versatile Mobile Apps with Python and REST. Berkeley, CA: Apress, 2020. http://dx.doi.org/10.1007/978-1-4842-6333-4.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Kurtz, Jamie, and Brian Wortman. ASP.NET Web API 2: Building a REST Service from Start to Finish. Berkeley, CA: Apress, 2014. http://dx.doi.org/10.1007/978-1-4842-0109-1.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

A Programmable Web: An Unfinished Work. Morgan & Claypool Publishers, 2013.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
8

Redmond, Paul. Lumen Programming Guide: Writing PHP Microservices, REST and Web Service APIs. Apress, 2016.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
9

Relan, Kunal. Building REST APIs with Flask: Create Python Web Services with MySQL. Apress, 2019.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
10

Guerrero, Sergio. Microservices in SAP HANA XSA: A Guide to REST APIs Using Node.js. Apress, 2020.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
More sources

Book chapters on the topic "APIs REST"

1

Lyu, Shing. "REST APIs." In Practical Rust Web Projects, 55–102. Berkeley, CA: Apress, 2021. http://dx.doi.org/10.1007/978-1-4842-6589-5_3.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Wirdemann, Ralf. "REST." In RESTful Go APIs, 27–37. München: Carl Hanser Verlag GmbH & Co. KG, 2019. http://dx.doi.org/10.3139/9783446459786.003.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Subramanian, Vasan. "Express REST APIs." In Pro MERN Stack, 69–91. Berkeley, CA: Apress, 2017. http://dx.doi.org/10.1007/978-1-4842-2653-7_5.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Varga, Ervin. "Testing REST APIs." In Creating Maintainable APIs, 159–69. Berkeley, CA: Apress, 2016. http://dx.doi.org/10.1007/978-1-4842-2196-9_10.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Varga, Ervin. "Versioning REST APIs." In Creating Maintainable APIs, 109–18. Berkeley, CA: Apress, 2016. http://dx.doi.org/10.1007/978-1-4842-2196-9_6.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Varga, Ervin. "Documenting REST APIs." In Creating Maintainable APIs, 143–57. Berkeley, CA: Apress, 2016. http://dx.doi.org/10.1007/978-1-4842-2196-9_9.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Sud, Kanika. "Understanding REST APIs." In Practical hapi, 1–11. Berkeley, CA: Apress, 2020. http://dx.doi.org/10.1007/978-1-4842-5805-7_1.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Varga, Ervin. "Implementing Synchronous and Asynchronous REST APIs." In Creating Maintainable APIs, 135–41. Berkeley, CA: Apress, 2016. http://dx.doi.org/10.1007/978-1-4842-2196-9_8.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Rawal, Pathik, and Pryank Rohilla. "Integration Using Yammer Rest APIs." In Develop on Yammer, 171–231. Berkeley, CA: Apress, 2015. http://dx.doi.org/10.1007/978-1-4842-0943-1_6.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Relan, Kunal. "CRUD Application with Flask (Part 2)." In Building REST APIs with Flask, 97–134. Berkeley, CA: Apress, 2019. http://dx.doi.org/10.1007/978-1-4842-5022-8_4.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Conference papers on the topic "APIs REST"

1

Serrano, Diego, Eleni Stroulia, Diana Lau, and Tinny Ng. "Linked REST APIs: A Middleware for Semantic REST API Integration." In 2017 IEEE International Conference on Web Services (ICWS). IEEE, 2017. http://dx.doi.org/10.1109/icws.2017.26.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Li, Li, and Wu Chou. "Designing Large Scale REST APIs Based on REST Chart." In 2015 IEEE International Conference on Web Services (ICWS). IEEE, 2015. http://dx.doi.org/10.1109/icws.2015.89.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Lachgar, Mohamed, Hanane Benouda, and Selwa Elfirdoussi. "Android REST APIs: Volley vs Retrofit." In 2018 International Symposium on Advanced Electrical and Communication Technologies (ISAECT). IEEE, 2018. http://dx.doi.org/10.1109/isaect.2018.8618824.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Godefroid, Patrice, Daniel Lehmann, and Marina Polishchuk. "Differential regression testing for REST APIs." In ISSTA '20: 29th ACM SIGSOFT International Symposium on Software Testing and Analysis. New York, NY, USA: ACM, 2020. http://dx.doi.org/10.1145/3395363.3397374.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Mayer, Simon. "Open APIs for the Rest of Us." In WoT 2017: Eighth International Workshop on the Web of Things. New York, NY, USA: ACM, 2017. http://dx.doi.org/10.1145/3199919.3199922.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Michelin, Regio A., Avelino F. Zorzo, and Cesar A. De Rose. "Mitigating DoS to authenticated cloud REST APIs." In 2014 9th International Conference for Internet Technology and Secured Transactions (ICITST). IEEE, 2014. http://dx.doi.org/10.1109/icitst.2014.7038787.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Diego Casagranda França, Marlon, and Eduardo Da Silva. "Performance Evaluation of REST and GraphQL APIs Searching Nested Objects." In Computer on the Beach. Itajaí: Universidade do Vale do Itajaí, 2020. http://dx.doi.org/10.14210/cotb.v11n1.p237-244.

Full text
Abstract:
With the growth of mobile devices claiming an increasing share ofinternet traffic, optimizing data search performance becomes important.REST architecture has been the most common solution todevelopWeb APIs, but GraphQL is becoming, recently, an attractivealternative. This paper discusses the REST and GraphQL techniquesfor data communication between Web applications. An experimentis also performed, to evaluate the performance of APIs implementingREST and GraphQL when requesting nested objects. Prototypesof each API were implemented to perform measurements of eachtechnique’s performance. Results show that GraphQL performedbetter in the most evaluated scenarios.
APA, Harvard, Vancouver, ISO, and other styles
8

Atlidakis, Vaggelis, Patrice Godefroid, and Marina Polishchuk. "Checking Security Properties of Cloud Service REST APIs." In 2020 IEEE 13th International Conference on Software Testing, Validation and Verification (ICST). IEEE, 2020. http://dx.doi.org/10.1109/icst46399.2020.00046.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Haupt, Florian, Frank Leymann, and Cesare Pautasso. "A Conversation Based Approach for Modeling REST APIs." In 2015 12th Working IEEE/IFIP Conference on Software Architecture (WICSA). IEEE, 2015. http://dx.doi.org/10.1109/wicsa.2015.20.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Serrano, Diego, and Eleni Stroulia. "The LRA Workbench for Composing Linked REST APIs." In 2018 IEEE World Congress on Services (SERVICES). IEEE, 2018. http://dx.doi.org/10.1109/services.2018.00028.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Reports on the topic "APIs REST"

1

Long, J. Lorenz APIs and REST Services. Office of Scientific and Technical Information (OSTI), April 2013. http://dx.doi.org/10.2172/1078546.

Full text
APA, Harvard, Vancouver, ISO, and other styles
We offer discounts on all premium plans for authors whose works are included in thematic literature selections. Contact us to get a unique promo code!

To the bibliography