rest-patterns

REST API design uses HTTP methods (GET, POST, PUT, PATCH, DELETE) with specific semantics: GET retrieves data idempotently, POST creates resources, PUT replaces entire resources idempotently, PATCH updates partial resources, DELETE removes resources. Enforcing correct method usage ensures predictable, cacheable, and safe API behavior across clients.

HTTP status codes standardize API responses: 2xx indicates success, 3xx redirects, 4xx signals client errors (400 bad request, 404 not found, 409 conflict), 5xx indicates server errors. Consistent status code usage helps clients handle responses correctly and improves API debuggability.

REST APIs use HTTP caching headers (Cache-Control, ETag, Last-Modified) to reduce server load and improve response times. Rate limiting enforces request quotas per client using headers or tokens, preventing abuse and ensuring fair resource allocation across users.

REST API versioning strategies include URL path versioning (v1/, v2/), header-based versioning, or query parameters. Versioning allows you to introduce breaking changes while maintaining backward compatibility, letting old clients continue working while new clients adopt improved endpoints.

Standardized error responses include consistent fields (error code, message, details), enabling clients to parse and handle failures predictably. Pagination using limit, offset, or cursor parameters lets clients retrieve large datasets incrementally without overloading the server.

HATEOAS (Hypermedia As The Engine Of Application State) embeds links in API responses, allowing clients to discover related resources and actions dynamically. This approach decouples clients from hardcoded endpoint URLs and enables more flexible, self-documenting APIs.