RESTful API Design Architect
Design a complete, production-ready API from scratch — endpoints, auth, error handling, versioning, and documentation.
From a single endpoint to full documentation with examples, errors, rate limits, and code samples
Here's my API endpoint: ``` [PASTE YOUR ROUTE/CONTROLLER CODE] ``` Generate production-ready documentation: 1. OVERVIEW — one-sentence description, HTTP method, path, auth required? 2. PARAMETERS — table with: name, type, required?, description, default value, validation rules, example 3. REQUEST EXAMPLE — complete curl command + JSON body with realistic data 4. RESPONSE — success response with full JSON example + field descriptions 5. ERROR RESPONSES — table of all possible errors: status code, error key, message, when it occurs, how to fix it 6. RATE LIMITS — if applicable 7. CODE EXAMPLES — JavaScript fetch, Python requests, curl Format as Markdown ready for docs site.
This prompt structures documentation using the same patterns developers expect from top-tier APIs (Stripe, Twilio). By requiring examples, error codes, and rate limits upfront, it produces docs that answer real developer questions immediately.
Use when shipping a new API endpoint and need comprehensive docs fast, when your existing docs are outdated and need regeneration from code, or when preparing developer-facing documentation for a product launch.
You'll get production-ready API documentation including endpoint descriptions, request/response examples with realistic data, error code tables, authentication instructions, and rate limit details—ready to publish.
Design a complete, production-ready API from scratch — endpoints, auth, error handling, versioning, and documentation.
Generate clear, maintainable technical documentation from code — README, API docs, architecture guides, and runbooks.
Bad error messages cost hours of debugging. This prompt creates clear, actionable error messages for every API endpoint.
Generate a professional README that turns visitors into users. With badges, examples, and a clear getting-started flow.
Transform product requirements into a complete REST or GraphQL API design with endpoints, schemas, and auth.