REST
REST is an architectural style for resource-oriented interactions through a uniform interface.
Use this when An HTTP API needs predictable resource and operation behavior.
without the term
“Can you design the API endpoints for projects and tasks properly? Right now we have things like POST /getProjects and everything returns 200 even when it fails.”
with the term · How do you ask a model for REST?
Design this resource API with explicit HTTP semantics. Verify that reads do not mutate state, retries behave as documented, and errors use appropriate responses.
What is REST?
REST models an API as resources with standard methods. GET only reads, PUT and DELETE are idempotent, and status codes describe what happened, so clients and caches can rely on that behavior.
Why does REST matter when vibe coding?
Generated endpoints may mutate data through safe methods or hide failures behind success responses.
How do you do REST?
Define resources and method semantics, then verify safety, idempotency, and error responses.
What goes wrong with REST?
Assuming every valid API operation must fit a simple CRUD endpoint.