Coding
TEXT
OpenAPI Specification Generator
April 1, 2026
Optimized for:
general
API design and documentation, generating API specs for new services, standardizing existing API documentation
You are an API design expert. Generate a complete OpenAPI 3.1 specification for the described API. **API Details:** - API Name: [API_NAME] - Base URL: [BASE_URL] - Version: [VERSION] - Description: [WHAT_THE_API_DOES] - Authentication: [Bearer JWT / API Key / OAuth2 / None] - Resources: [LIST_YOUR_RESOURCES, e.g., users, products, orders] **For each resource, generate:** 1. **Paths**: All CRUD endpoints plus any custom actions - Proper HTTP methods (GET, POST, PUT, PATCH, DELETE) - Path parameters with descriptions - Query parameters for filtering, pagination, sorting - Request bodies with required/optional fields - All possible response codes (200, 201, 204, 400, 401, 403, 404, 409, 422, 500) 2. **Schemas** (components/schemas): - Request schemas (Create, Update with partial fields) - Response schemas (single item, paginated list) - Error schema with code, message, details array - Enum types for status fields - Proper use of allOf, oneOf, anyOf for schema composition 3. **Security Schemes**: Define authentication with examples 4. **Tags**: Group endpoints logically with descriptions 5. **Examples**: Provide realistic request/response examples for every endpoint 6. **Pagination**: Use cursor-based or offset pagination with Link headers 7. **Rate Limiting**: Document rate limit headers (X-RateLimit-Limit, X-RateLimit-Remaining) **Output Format:** Valid YAML OpenAPI 3.1 specification that can be imported directly into Swagger UI, Postman, or any OpenAPI-compatible tool. Include inline comments explaining design decisions.
Generates complete OpenAPI 3.1 specifications with schemas, examples, authentication, pagination, and rate limiting documentation.
Submit your own AI prompts to the community. The best ones get featured on TokenCalculator - and credited to you.