RESTful API Design Architect
Design a complete, production-ready API from scratch — endpoints, auth, error handling, versioning, and documentation.
Transform product requirements into a complete REST or GraphQL API design with endpoints, schemas, and auth.
You are a senior API architect with 15 years of experience designing scalable APIs for companies like Stripe, Twilio, and GitHub. Design a complete API architecture based on these requirements: Project: [PROJECT NAME] Type: [REST / GraphQL / both] Requirements: [LIST YOUR FEATURES AND USE CASES] Deliver: 1. **Resource Model** — List all resources/entities with relationships (1:1, 1:N, N:N) 2. **Endpoint Design** — For each resource: - Method + path (RESTful conventions) - Request/response schema (TypeScript interfaces) - Query parameters for filtering, pagination, sorting 3. **Authentication & Authorization** - Auth strategy (JWT, API keys, OAuth2) - Permission model (roles, scopes, resource ownership) 4. **Error Handling** - Standard error response format - Common error codes with examples 5. **Versioning Strategy** — How to handle breaking changes 6. **Rate Limiting** — Tiers and limits per endpoint 7. **Pagination** — Cursor vs offset, default page sizes 8. **Webhooks** — Events to expose, payload format, retry policy Follow these principles: - Consistent naming conventions - Idempotent operations where possible - HATEOAS links for discoverability - OpenAPI 3.0 compatible
Good API design prevents years of technical debt. This prompt applies REST and GraphQL design principles—resource modeling, versioning strategy, and authentication patterns—to produce a comprehensive API blueprint before you write any code.
Use when starting a new backend service and need to design endpoints from requirements, when migrating from a monolith to microservices, or when planning a public API that external developers will consume.
You'll get a complete API design document including resource definitions, endpoint specifications, authentication flow, versioning strategy, pagination approach, and error response standards—ready for team review and implementation.
Design a complete, production-ready API from scratch — endpoints, auth, error handling, versioning, and documentation.
Design a normalized, scalable database schema from a project description — tables, relationships, indexes, and queries.
Practice system design interviews with a realistic AI interviewer — get architecture feedback, follow-up questions, and…
Plan your monorepo structure, tooling, CI/CD, and dependency management before writing a single line of code.
Stop forgetting why you made that technical decision 6 months ago. This prompt creates a complete ADR in 2 minutes.