HELP AND REFERENCE
Error dictionary
Find a support code, understand the reason and choose a safe next step.
280 support codes · 253 reason codes · Generated from Zaqnet’s shared catalogue
Before retrying a change
If a save, payment, stock movement or conversion timed out, check the record and its history first. An error response does not prove the operation was rejected. Do not create a duplicate while the outcome is uncertain.
The five-digit code identifies the service and failure class. A reason code narrows the cause. Some client messages have no numeric code, and your deployed version may differ from this catalogue.
533 entries · 1–20
identity · Support code10101 Invalid request
The request could not be processed because one or more fields are missing, malformed, or inconsistent with the API contract.
What to do next
- Review the request fields and required inputs.
- Retry after correcting the invalid value or missing field.
If it continues, send support the code, any reason code, request identifier, approximate time and action attempted. Keep passwords, tokens and unnecessary personal information out of the request.
identity · Support code10201 Invalid credentials
The supplied credentials were not accepted.
What to do next
- Retry with the correct sign-in method and credentials.
- Reset the password if access is still blocked.
If it continues, send support the code, any reason code, request identifier, approximate time and action attempted. Keep passwords, tokens and unnecessary personal information out of the request.
identity · Support code10202 Invalid or expired token
The current session token could not be verified.
What to do next
- Sign in again and retry the request.
- Refresh the session if the client supports silent renewal.
If it continues, send support the code, any reason code, request identifier, approximate time and action attempted. Keep passwords, tokens and unnecessary personal information out of the request.
identity · Support code10210 Authentication required
The request requires a valid authenticated identity.
What to do next
- Sign in and try again.
- Make sure the request includes the required auth header.
If it continues, send support the code, any reason code, request identifier, approximate time and action attempted. Keep passwords, tokens and unnecessary personal information out of the request.
identity · Support code10301 Resource already exists
The system rejected the request because a resource with the same unique identity already exists.
What to do next
- Check if the record was already created before retrying.
- Use the existing record instead of creating a duplicate.
If it continues, send support the code, any reason code, request identifier, approximate time and action attempted. Keep passwords, tokens and unnecessary personal information out of the request.
identity · Support code10302 Duplicate constrained value
A value that must stay unique is already in use.
What to do next
- Retry with a different unique value.
- Check whether this value already belongs to an existing record.
If it continues, send support the code, any reason code, request identifier, approximate time and action attempted. Keep passwords, tokens and unnecessary personal information out of the request.
identity · Support code10401 Unauthorized caller
The caller is not authorized to access this route or resource.
What to do next
- Use an account or token with the correct access level.
- Retry through the supported product flow instead of a restricted endpoint.
If it continues, send support the code, any reason code, request identifier, approximate time and action attempted. Keep passwords, tokens and unnecessary personal information out of the request.
identity · Support code10402 Permission denied
The request was understood, but the current identity does not have permission to perform this action.
What to do next
- Ask an authorized admin to perform the action or grant access.
- Refresh the page if permissions or membership changed recently.
If it continues, send support the code, any reason code, request identifier, approximate time and action attempted. Keep passwords, tokens and unnecessary personal information out of the request.
identity · Support code10409 Resource state conflict
The request conflicts with the current state of the resource.
What to do next
- Refresh the resource and review its latest status.
- Retry only if the resource returns to a valid state.
If it continues, send support the code, any reason code, request identifier, approximate time and action attempted. Keep passwords, tokens and unnecessary personal information out of the request.
identity · Support code10901 Internal service failure
The request failed due to an unexpected internal error.
What to do next
- Retry once if the action is safe to repeat.
- Contact support with the request ID if the issue continues.
If it continues, send support the code, any reason code, request identifier, approximate time and action attempted. Keep passwords, tokens and unnecessary personal information out of the request.
identity · Support code10902 Resource not found
The requested record or related dependency could not be found.
What to do next
- Check that the correct record or reference was used.
- Refresh and retry if the record was just created.
If it continues, send support the code, any reason code, request identifier, approximate time and action attempted. Keep passwords, tokens and unnecessary personal information out of the request.
identity · Support code10903 Dependency unavailable
A required downstream service or infrastructure dependency is unavailable.
What to do next
- Retry after a short wait.
- Contact support if the issue persists across multiple attempts.
If it continues, send support the code, any reason code, request identifier, approximate time and action attempted. Keep passwords, tokens and unnecessary personal information out of the request.
identity · Support code10904 Feature not implemented
The requested capability is not available in the current build.
What to do next
- Use the currently supported workflow for this operation.
- Check product release notes or contact support for rollout timing.
If it continues, send support the code, any reason code, request identifier, approximate time and action attempted. Keep passwords, tokens and unnecessary personal information out of the request.
identity · Support code10920 Rate limited
Too many requests were made in a short period of time.
What to do next
- Wait briefly and retry.
- Avoid repeating the same action rapidly.
If it continues, send support the code, any reason code, request identifier, approximate time and action attempted. Keep passwords, tokens and unnecessary personal information out of the request.
directory · Support code11101 Invalid request
The request could not be processed because one or more fields are missing, malformed, or inconsistent with the API contract.
What to do next
- Review the request fields and required inputs.
- Retry after correcting the invalid value or missing field.
If it continues, send support the code, any reason code, request identifier, approximate time and action attempted. Keep passwords, tokens and unnecessary personal information out of the request.
directory · Support code11201 Invalid credentials
The supplied credentials were not accepted.
What to do next
- Retry with the correct sign-in method and credentials.
- Reset the password if access is still blocked.
If it continues, send support the code, any reason code, request identifier, approximate time and action attempted. Keep passwords, tokens and unnecessary personal information out of the request.
directory · Support code11202 Invalid or expired token
The current session token could not be verified.
What to do next
- Sign in again and retry the request.
- Refresh the session if the client supports silent renewal.
If it continues, send support the code, any reason code, request identifier, approximate time and action attempted. Keep passwords, tokens and unnecessary personal information out of the request.
directory · Support code11210 Authentication required
The request requires a valid authenticated identity.
What to do next
- Sign in and try again.
- Make sure the request includes the required auth header.
If it continues, send support the code, any reason code, request identifier, approximate time and action attempted. Keep passwords, tokens and unnecessary personal information out of the request.
directory · Support code11301 Resource already exists
The system rejected the request because a resource with the same unique identity already exists.
What to do next
- Check if the record was already created before retrying.
- Use the existing record instead of creating a duplicate.
If it continues, send support the code, any reason code, request identifier, approximate time and action attempted. Keep passwords, tokens and unnecessary personal information out of the request.
directory · Support code11302 Duplicate constrained value
A value that must stay unique is already in use.
What to do next
- Retry with a different unique value.
- Check whether this value already belongs to an existing record.
If it continues, send support the code, any reason code, request identifier, approximate time and action attempted. Keep passwords, tokens and unnecessary personal information out of the request.
Need help with a message that is not listed?
Use the exact wording from the app and describe the action that triggered it. Include the record identifier and whether you have checked for an existing save.
Contact Zaqnet support · Services status