Pith. sign in

REVIEW 2 cited by

LRASGen: LLM-based RESTful API Specification Generation

Not yet reviewed by Pith; the record is open.

This paper has not been read by Pith yet. Machine review is queued; the pith claim, tier, and objections will appear here once it completes.

SPECIMEN: schema-true, not a live event

T0 review · schema-true

One-sentence machine reading of the paper's core claim.

pith:XXXXXXXX · record.json · timestamp

arxiv 2504.16833 v1 pith:3HQZAVFW submitted 2025-04-23 cs.SE

classification cs.SE
keywords restfulapiscodegenerationllmslrasgenspecificationsgenerate
verification ladder T0 review T1 audit T2 compute T3 formal
0 comments
read the original abstract

REpresentation State Transfer (REST) is an architectural style for designing web applications that enable scalable, stateless communication between clients and servers via common HTTP techniques. Web APIs that employ the REST style are known as RESTful (or REST) APIs. When using or testing a RESTful API, developers may need to employ its specification, which is often defined by open-source standards such as the OpenAPI Specification (OAS). However, it can be very time-consuming and error-prone to write and update these specifications, which may negatively impact the use of RESTful APIs, especially when the software requirements change. Many tools and methods have been proposed to solve this problem, such as Respector and Swagger Core. OAS generation can be regarded as a common text-generation task that creates a formal description of API endpoints derived from the source code. A potential solution for this may involve using Large Language Models (LLMs), which have strong capabilities in both code understanding and text generation. Motivated by this, we propose a novel approach for generating the OASs of RESTful APIs using LLMs: LLM-based RESTful API-Specification Generation (LRASGen). To the best of our knowledge, this is the first use of LLMs and API source code to generate OASs for RESTful APIs. Compared with existing tools and methods, LRASGen can generate the OASs, even when the implementation is incomplete (with partial code, and/or missing annotations/comments, etc.). To evaluate the LRASGen performance, we conducted a series of empirical studies on 20 real-world RESTful APIs. The results show that two LLMs (GPT-4o mini and DeepSeek V3) can both support LARSGen to generate accurate specifications, and LRASGen-generated specifications cover an average of 48.85% more missed entities than the developer-provided specifications.

Discussion (0). Continue with ORCID to comment.

Forward citations

Cited by 2 Pith papers

Reviewed papers in the Pith corpus that reference this work. Sorted by Pith novelty score. Full citation record

  1. OOPS: Automated generation of REST API specification via LLMs

    cs.SE 2026-01 conditional novelty 6.0 of 10

    OOPS uses LLM agents and an API dependency graph to generate OpenAPI specs from REST API server code across multiple languages and frameworks, with reported F1 above 92% on 12 APIs.

  2. SAINT: Service-level Integration Test Generation with Program Analysis and LLM-based Agents

    cs.SE 2025-11 conditional novelty 6.0 of 10

    SAINT automatically generates both endpoint-level and scenario-based REST API tests for enterprise Java apps using static analysis and LLM agents, outperforming EvoMaster on code coverage in several benchmarks.

Pith tools