VOOZH about

URL: https://apistylebook.com/design/topics/http-status-400

⇱ 400 Bad Request

400 Bad Request

The server cannot or will not process the request due to an apparent client error (e.g., malformed request syntax, too large size, invalid request message framing, or deceptive request routing).

Cloud Foundry - Cloud Controller API v3 Style Guide (Proposal)

Client Errors

Deliveroo - API Design

POST, creating entities
400 Bad Request if the entity cannot be created with the information in the request body
PATCH, mutating entities
400 Bad Request, if the modification failed.
Return codes and errors
400 Bad Request: bad syntax (unknown route, missing required fields or parameters, unknown extra parameters, bad field or parameter values).
Parameters
Those endpoints may return 400 Bad Request if parameters are specified.

Haufe - Haufe API style guide

HTTP Status (Get List of resources)
HTTP Status (Update Single Resource)
HTTP Status (Update Partial Single Resource)
HTTP Status Codes

PayPal - API Style Guide

HTTP Status (Collections)

White House - White House Web API Standards

Error handling

Zalando - RESTFul API Guidelines

Client Side Error Codes

adidas - adidas API design guidelines

Security