Some of the scenarios in API update and create flows in publisher REST APIs are returning incorrect HTTP status codes and error descriptions, often resulting in a 500 - Internal Server Error, which misleads API developers who apply changes to the APIs using the RESTful approach. This is observed much when an incorrect payload is passed to the rest api. So the response error codes should be 400 instead of 500. And proper error description should be returned as well.
Solution
Handle error scenarios in REST api implementation properly and introducing Error Handlers properly
Problem
Some of the scenarios in API update and create flows in publisher REST APIs are returning incorrect HTTP status codes and error descriptions, often resulting in a 500 - Internal Server Error, which misleads API developers who apply changes to the APIs using the RESTful approach. This is observed much when an incorrect payload is passed to the rest api. So the response error codes should be 400 instead of 500. And proper error description should be returned as well.
Solution
Handle error scenarios in REST api implementation properly and introducing Error Handlers properly
Affected Component
APIM
Version
No response
Implementation
No response
Related Issues
No response
Suggested Labels
No response