backend-api-design-review

Review REST API design by verifying resource modeling, HTTP method usage, status codes, and idempotency to catch endpoint issues before they reach clients. This ensures correct HTTP semantics and consistent contract quality across controllers and route handlers.

Auditing GraphQL resolvers involves evaluating versioning, error response shapes, pagination, filtering, and validation to find issues that would break client expectations. This resolver review ensures representation consistency and contract quality during implementation.

Checking HTTP status codes and idempotency in API controllers involves verifying HTTP semantics and resource modeling during endpoint audits. This process confirms that route handlers return correct status codes and maintain safe, idempotent operations for reliable client interactions.

This API review covers pagination, filtering, and error shapes for contract changes by evaluating versioning and representation consistency across endpoints. It ensures that validation and error response shapes remain uniform during endpoint audits and contract modifications.

API design breaks client expectations during contract changes when versioning, error response shapes, and representation consistency are not properly maintained. Reviewing endpoint semantics and validation rules catches these contract flaws before release.