Framework Support
EasyApi understands standard HTTP frameworks out of the box — you do not need any configuration or rule files to export APIs from projects using them. EasyApi automatically recognizes the framework's annotations and generates the corresponding API documentation.
Default Support
| Framework | Description |
|---|---|
| Spring MVC | Most widely used Java web framework (@RestController, @RequestMapping, etc.) |
| Spring WebFlux | Reactive web framework (Mono / Flux / Publisher) |
| Spring Actuator | Spring Boot Actuator endpoints |
| Feign | Spring Cloud OpenFeign client interfaces (@FeignClient) |
| JAX-RS | Java RESTful Web Services standard (Quarkus / Jersey) |
| gRPC | High-performance RPC framework |
| Custom | Rule-driven support for project-specific API conventions |
When You Need Custom Rules
For the frameworks above, export works without any rule files. You only need custom rules when something changes the request/response contract invisibly — for example a servlet filter that requires a header, or a response wrapper that envelopes every response. In those cases, use the built-in AI Assistant or the external skill to detect the pattern and generate the rule.
Common Support
| Framework/Spec | Description |
|---|---|
| javax.validation | Java Bean Validation specification |
| Jakarta Validation | Jakarta Bean Validation specification |
| Swagger | API documentation specification (v2) |
| Swagger 3 / OpenAPI | API documentation specification (v3) |
| Jackson | JSON serialization/deserialization |
| Gson | Google JSON library |
| Fastjson | Alibaba JSON library |
Built-in Extensions
| Extension | Description |
|---|---|
| Deprecated & Converts | Deprecated info and type conversions |
| Field Order | Field ordering extensions |
| Spring Configuration | Spring config properties support |