Design a clean, versioned REST API with consistent resources, status codes, pagination, errors, and an OpenAPI contract.
## CONTEXT I am designing a REST API that other teams or external clients will consume, and I want it to be predictable, well documented, and hard to misuse. I want consistent naming, sensible status codes, robust error shapes, pagination, and a versioning strategy that lets me evolve without breaking clients. I…
Premium Prompt
Unlock this prompt — and all 30,000+ expert-crafted prompts — with Pro.
Unlock with Pro