API Documentation Completeness Check on your current API documentation and generate a detailed review report. Based on this report, you can refine and improve your documentation β making collaboration smoother, the docs easier to read, and all AI features more effective thanks to more accurate endpoint specs.API Documentation Completeness Check, it's helpful to review whether the descriptions and definitions in the current API documentation are complete. The check analyzes the following aspects:| Element | Purpose |
|---|---|
| Request Method | Defines the HTTP method (GET, POST, PUT, DELETE) to determine request semantics, idempotency, and parameter structure |
| Request Path | The full URL path (excluding base URL) to uniquely identify the endpoint and infer path parameter structure |
| Endpoint Name and Description | Short explanation of the endpoint's purpose to help readers and AI understand business logic |
| Element | Purpose |
|---|---|
| Parameter Name | Ensures parameter structure is complete, naming is consistent, and each parameter is in the correct location (Params, Body, Headers, Cookies) |
| Example | Provides valid sample input values to help understand typical values, formats, data types, and business meaning |
| Description | Explains the meaning, purpose, and business scenarios of the parameter |
| Constraint | Purpose |
|---|---|
| Required/Nullable | Indicates whether a parameter is required and whether null values are allowed |
| Enums/Const | Lists possible enum or constant values and their meanings |
| Boundary Values | Provides minimum/maximum values, length limits, and other constraints |
| Format | Describes special formats (date-time, email, uuid, binary, int64, json-string, etc.) |
| Element | Purpose |
|---|---|
| Response Body | Provides complete structure for response content type, field explanations, HTTP status codes, and error codes |
API Documentation Completeness Check feature in the upper-right corner of an endpoint documentation page. Click it to start the check.