July 2017
Beginner to intermediate
358 pages
10h 54m
English
In the instance of failure, users of your API should be able to write one piece of code that handles errors across different endpoints. A standard error entity will help your consumers by enabling them to write DRY code whenever an error caused by client or server occurs.
The Microsoft API guidelines recommend the following format for these entities:
{ "error": { "code": "BadArgument", "message": "Previous passwords may not be reused", "target": "password", "innererror": a { "code": "PasswordError", "innererror": { "code": "PasswordDoesNotMeetPolicy", "minLength": "6", "maxLength": "64", "characterTypes": ["lowerCase","upperCase","number","symbol"], "minDistinctCharacterTypes": "2", "innererror": { "code": "PasswordReuseNotAllowed" ...Read now
Unlock full access