How should a RESTful API be designed to handle complex error responses consistently, including validation errors affecting multiple fields at once?

A well designed API typically returns a consistent, structured error response format for every type of failure, including a clear top level error message along with, for validation failures specifically, a detailed breakdown identifying exactly which individual fields failed validation and why, all using an appropriate HTTP status code, which lets client applications programmatically handle errors consistently across every single endpoint rather than needing custom error parsing logic for each different API operation.

http_response_code(422);
echo json_encode([
    'message' => 'Validation failed',
    'errors' => ['email' => ['The email field is required'], 'age' => ['The age must be at least 18']]
]);