# Opportunities in Software Engineering Research for Web API Consumption

**Authors:** Erik Wittern, Annie Ying, Yunhui Zheng, Jim A. Laredo, Julian Dolby,, Christopher C. Young, Aleksander A. Slominski

arXiv: 1705.06586 · 2017-05-19

## TL;DR

This paper discusses the challenges of consuming web APIs in software engineering and proposes research opportunities, including API specification curation and static analysis, to improve developer support and IDE integration.

## Contribution

It introduces new research directions in web API specification curation and static analysis, and demonstrates combining these for enhanced IDE support.

## Key findings

- Identification of key challenges in web API consumption
- Proposal of methods for API specification curation and static analysis
- Initial work on integrating these methods into IDE support

## Abstract

Nowadays, invoking third party code increasingly involves calling web services via their web APIs, as opposed to the more traditional scenario of downloading a library and invoking the library's API. However, there are also new challenges for developers calling these web APIs. In this paper, we highlight a broad set of these challenges and argue for resulting opportunities for software engineering research to support developers in consuming web APIs. We outline two specific research threads in this context: (1) web API specification curation, which enables us to know the signatures of web APIs, and (2) static analysis that is capable of extracting URLs, HTTP methods etc. of web API calls. Furthermore, we present new work on how we combine (1) and (2) to provide IDE support for application developers consuming web APIs. As web APIs are used broadly, research in supporting the consumption of web APIs offers exciting opportunities.

## Full text

_Full body text omitted from this summary view._ Fetch the complete paper as Markdown: https://tomesphere.com/paper/1705.06586/full.md

## Figures

2 figures with captions in the complete paper: https://tomesphere.com/paper/1705.06586/full.md

## References

27 references — full list in the complete paper: https://tomesphere.com/paper/1705.06586/full.md

---
Source: https://tomesphere.com/paper/1705.06586