Error handling
Resolve common integration errors and validation issues by identifying root causes and applying the recommended corrective actions
Common errors
Some common errors may occur, and it is important to know the causes and recommend corrective actions to effectively address them.
List of errors
Expand all
Case
This error occurs due to an unexpected condition on the server.
Recommendation
Retry the request after some time. If the error persists, contact Chargebackhit support with the error details.
Case
The specified resource could not be found, such as an invalid UUID.
Recommendation
Verify the resource identifier and ensure it exists before making the request.
Case
The server could not understand the request due to invalid syntax.
Recommendation
Check the request format and parameters.
Case
The request contains invalid data that does not meet the validation criteria.
Recommendation
Review the validation error details provided in the response and correct the input data accordingly.
Case
The request lacks valid authentication credentials.
Recommendation
Ensure the correct API keys are used and included in the request headers.
Validation errors
Various validation errors can occur, and it is vital to understand the conditions that cause them and the recommended actions to correct them.
List of errors
Expand all
Case
Cannot be blank, a required field is missing or empty.
Recommendation
Provide a value for the required field.
Case
Cannot be null or empty, a field that should not be null or empty is null or empty.
Recommendation
Ensure the field has a non-null and non-empty value.
Case
The length must be no more than {{.max}}, a field value exceeds the maximum allowed length.
Recommendation
Shorten the field value to meet the length requirement.
Case
The length must be no less than {{.min}}, a field value is shorter than the minimum required length.
Recommendation
Increase the field value to meet the length requirement.
Case
The length must be exactly {{.min}}, a field value does not meet the exact length requirement.
Recommendation
Adjust the field value to meet the exact length.
Case
The length must be between {{.min}} and {{.max}}, a field value does not fall within the specified length range.
Recommendation
Modify the field value to fall within the required range.
Case
The value must be empty, a field value is not empty when it should be.
Recommendation
Clear the value of the field.
Case
Must be a valid email address, a field value is not a valid email address.
Recommendation
Provide a valid email address format for the field.
Case
Must contain digits only, a field value contains non-digit characters.
Recommendation
Ensure the field value contains only digits.
Case
Must be a valid UUID, a field value is not a valid UUID.
Recommendation
Provide a valid UUID format for the field.
Case
Must be a valid value, a field value is not within the acceptable range or set of values.
Recommendation
Use a valid value that is acceptable for the field.
Case
Status must be a valid value, the status of the MID is not suitable for the requested operation.
Recommendation
Verify the current status of the MID and ensure it meets the requirements for the operation, contact support if further assistance is needed.
