# Supported HTTP Error Status Codes
source: https://developer.mastercard.com/riskrecon-api/documentation/code-and-formats/supp-http-err-cds/index.md

A list of possible error codes is provided in the following table. These error codes are returned along with additional information about how to resolve them.

|      HTTP Status Code      |                                                                                                      Description                                                                                                      |                                                Resolution Tip                                                |
|----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------|
| BAD_REQUEST (400)          | The request failed because it contained an invalid value or missing required value. The value could be a parameter value, a header value, or a property value.                                                        | Please correct the request as per the error description or details provided in the error response.           |
| UNAUTHORIZED (401)         | The user does not have valid authentication credentials for the target resource. This could be because the user is using a bad, missing, or expired JSON token to authenticate.                                       | Please ensure that a valid JSON token is used while calling the RiskRecon APIs.                              |
| NOT_FOUND (404)            | The requested resource or endpoint was not found as it does not exist.                                                                                                                                                | Please enter the correct API endpoint URL.                                                                   |
| UNPROCESSABLE ENTITY (422) | The request failed because the request body contains a parameter value which does not match the validation rules or specified requirements. Hence, although the server understands the request, it cannot process it. | Please correct the request as per the error description or details provided in the error response.           |
| TOO_MANY_REQUESTS (429)    | The request failed because the user has crossed the maximum rate limit specified for the endpoint.                                                                                                                    | Please correct the request as per the error description or details provided in the error response and retry. |