This commit is contained in:
@@ -125,7 +125,7 @@ Here is an example of a more detailed error response showing validation errors o
|
||||
{
|
||||
"message": "255 max",
|
||||
"target": "Name",
|
||||
"error": "LengthExceeded"
|
||||
"error": "2202"
|
||||
},
|
||||
{
|
||||
"target": "EndDate",
|
||||
@@ -147,7 +147,7 @@ The above example shows multiple validation errors ([API error code](api-error-c
|
||||
|
||||
`target` property shows the location of the error. The value of `target` is either a property name corresponding to the property that failed business rule validation or blank if the validation rule applies to the entire object in general.
|
||||
|
||||
`error` property contains the exact [validation error](api-validation-error-codes.md).
|
||||
`error` property contains the exact [api validation error code](api-error-codes.md).
|
||||
|
||||
`message` property optionally contains further information of use to the developer, in the example above you can see that the name property has more than the maximum limit of 255 characters.
|
||||
|
||||
@@ -219,4 +219,4 @@ Internal server errors are returned with an HTTP Status Code of 500 and an error
|
||||
|
||||
For security reasons no details of an internal server exception are returned, you must examine the [server log](common-log.md) to see the details.
|
||||
Generally this means the request triggered an unhandled exception which will be logged in detail to the log file.
|
||||
Please report any internal server errors (preferrably with the log showing the exception details) to AyaNova support so we can look into it.
|
||||
Please report any unexpected internal server errors (preferrably with the log showing the exception details) to AyaNova support so we can look into it.
|
||||
|
||||
Reference in New Issue
Block a user