Missing 4xx response

owasp:api2:2019-define-error-validation

Rule Severity:

High

Ensure API specifications include definitions for 400, 422, and 4XX responses.
This rule applies at the API Specification level (OAS/Swagger).
APIs endpoints that do not return HTTP status codes descriptions are more difficult to use for developers. Adding standard responses to API specifications ensures use of those APIs is predictable and safe.

1. How to Identify with Example Scenario

Find the text in bold to identify issues such as these in API specifications

responses: '200': # missing '400' response definition description: OK content: text/plain: schema: type: string

2. How to Identify with Example Scenario

Find the text in bold to identify issues such as these in API specifications

responses: '200': # missing '422' response definition description: OK content: text/plain: schema: type: string

1. How to Resolve with Example Scenario

Find the text in bold to identify issues such as these in API specifications

responses: '400': description: Unauthorized # a description is required content: text/plain: schema: type: string

2. How to Resolve with Example Scenario

Modify the text in bold to resolve issues such as these in API specifications

responses: '422': description: Unauthorized # a description is required content: text/plain: schema: type: string

References: