Which RESTful API Design Rules Are Important and How Do They Improve Software Quality? A Delphi Study with Industry Experts
Sebastian Kotstein, Justus Bogner

TL;DR
This study identifies and ranks the importance of REST API design rules based on expert opinions, highlighting which rules most significantly impact software quality attributes like usability and maintainability.
Contribution
It provides a prioritized list of REST API design rules based on industry expert consensus, guiding better API design practices.
Findings
28 rules rated highly important by experts
Usability, maintainability, and compatibility are most impacted quality attributes
Rules for reaching Richardson maturity level 2 are critical
Abstract
Several studies analyzed existing Web APIs against the constraints of REST to estimate the degree of REST compliance among state-of-the-art APIs. These studies revealed that only a small number of Web APIs are truly RESTful. Moreover, identified mismatches between theoretical REST concepts and practical implementations lead us to believe that practitioners perceive many rules and best practices aligned with these REST concepts differently in terms of their importance and impact on software quality. We therefore conducted a Delphi study in which we confronted eight Web API experts from industry with a catalog of 82 REST API design rules. For each rule, we let them rate its importance and software quality impact. As consensus, our experts rated 28 rules with high, 17 with medium, and 37 with low importance. Moreover, they perceived usability, maintainability, and compatibility as the most…
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
