Error Catalog
Snyk Error Codes
The error codes in the table below describe the codes that you may encounter while working with the Snyk API or CLI. When errors are encountered using the API, they will also have an appropriate HTTP status code. If you encounter errors without an error code, use the HTTP status code to determine the appropriate action.
Too many requests
The service has received too many requests and will be throttled.
HTTP Status: 429
Not implemented
The server either does not recognize the request method, or it lacks the ability to fulfil the request.
HTTP Status: 501
Bad request
The server cannot or will not process the request due to an apparent client error (e.g. malformed request syntax, size too large, invalid request message framing, or deceptive request routing).
HTTP Status: 400
Timeout error
The server did not receive a timely response from the upstream server.
HTTP Status: 504
Unauthorised error
Authentication failed or has not been provided.
HTTP Status: 401
Server error
An unexpected server error was encountered.
HTTP Status: 500
OpenAPI
Bad request
The request sent to the server is invalid or corrupt.
HTTP Status: 400
Forbidden
Access to the requested resource is forbidden.
HTTP Status: 403
Not acceptable
The server cannot provide a response which matches the provided accept headers.
HTTP Status: 406
Not found
The server cannot find the requested resource.
HTTP Status: 404
Method not allowed
The endpoint does not support the request method.
HTTP Status: 405
Request entity too large
The request entity exceeds server limitations.
HTTP Status: 413
Unauthorized
The request lacks authentication credentials for the requested resource.
HTTP Status: 401
Unsupported media type
The media format of the request is not supported.
HTTP Status: 415
Unsupported Ecosystem
The language or package manager is not supported.
HTTP Status: 400
Help Links:
Unable to parse manifest file
The provided manifest file could not be parsed as it has invalid syntax or does not match the expected schema.
HTTP Status: 400
Lock file out of sync with manifest file
Some of the dependencies that are expected to be in the lock file are missing - this usually indicates that the lock file is out of sync with the provided manifest file. Please re-sync the lock file and try again.
HTTP Status: 400
Unable to parse lock file
The provided lock file could not be parsed as it has invalid syntax or does not match the expected schema.
HTTP Status: 400
Unknown dependency version
Dependency version could not be resolved.
HTTP Status: 404
Help Links:
Missing required elements in payload
Elements required to serve this request was not found in the payload. See error details for specifics.
HTTP Status: 422
Unprocessable file
Found files that are not supported by this dependency service.
HTTP Status: 422
Failed to access private module
Your go.mod file contained private modules that Snyk was unable to access.
HTTP Status: 400
No go mod file found
A go.mod file was not found in current directory or any parent directory.
HTTP Status: 400
OAuth re-authorization required
As Snyk needs a temporary clone of your code to analyze its dependencies, your code is cloned on an isolated environment using Git.
Your organization has enabled or enforced SAML SSO after you authorized Snyk to access your code, and a re-authentication is therefore required.
The error you're seeing is usually reproducible by attempting to do a git clone of your repository with incorrectly configured credentials. In this case, please verify your authentication configuration with your Git cloud provider and try again.
HTTP Status: 422
Help Links:
Your project repository is missing required files
A part of generating the dependency graph requires Snyk to run go list -deps -json inside the project. If that operation for some reason fails, we're unable to continue, if we're to create a full dependency graph.
This error usually means that you either are missing some cleanup (e.g. go mod tidy) or that your project deployment process contains a code generation step (e.g. protobuf or the like) that Snyk does not know about.
A way to quickly verify if this is the case, try and clone your project in a clean environment and run go list -deps -json and verify whether the operation fails or not.
In this case Snyk is not able to process your code successfully and we suggest instead inserting the Snyk CLI as a part of your deployment pipeline.
HTTP Status: 422
Help Links:
Builds
Invalid request
The provided request payload is not valid for the selected ecosystem. Please review the API documentation.
HTTP Status: 400
Help Links:
Build environment not found
The build environment for the provided context could not be found. Please ensure you have created the build environment first.
HTTP Status: 404
SbomExport
Internal Server Error
Apologies, unfortunately an unexpected error has occurred. Please try again shortly. If the error persists please contact the Snyk support team.
HTTP Status: 500
Error while getting dependency graph
Apologies, unfortunately an unexpected error has occurred. Please try again shortly. If the error persists please contact the Snyk support team.
HTTP Status: 500
Error parsing dependency graph
Apologies, unfortunately an unexpected error has occurred. Please try again shortly. If the error persists please contact the Snyk support team.
HTTP Status: 500
Not Found
This is either a Snyk Code or Snyk Infrastructure as Code project. We don’t currently provide an SBOM for these project types.
HTTP Status: 404
We do not currently provide an SBOM document for this project type
Unsupported Snyk project type.
HTTP Status: 404
Unsuccessful request
Unsuccessful dep-graph request.
HTTP Status: 404
Unauthorized
Missing API token.
HTTP Status: 401
The body of the request can not be empty
The body of the request is empty.
HTTP Status: 400
The provided depgraph in the body is invalid
The provided dephgraph in the body is invalid.
HTTP Status: 400
Workspaces
Unauthorized Credentials
The credentials that have been provided could not be authorized with the upstream service.
HTTP Status: 401
Insufficient Privileges
The access token that has been provided has insufficient privileges to complete the requested operation with the upstream service.
HTTP Status: 401
Invalid Credentials
The credentials provided do to match the expected format.
HTTP Status: 400
Invalid Token
The workspace token provided is invalid.
HTTP Status: 400
Missing Access Token
The request is missing the access token.
HTTP Status: 401
Unauthorized Request
The provided token could not be authorized.
HTTP Status: 401
Target Not Found
The requested target could not be found. Please ensure the target details are correct.
HTTP Status: 404
Invalid Target
The target information that has been provided is in an invalid format.
HTTP Status: 400
File Size Error
The requested file is too large to be transferred.
HTTP Status: 400
File Not Found
The requested file could not be found. Please ensure the file path exists in the provided target.
HTTP Status: 404
Too Many Requests
The upstream service has received too many requests and will be throttled.
HTTP Status: 429
Service Unavailable
The upstream service is unavailable.
HTTP Status: 502
Maven Search Service Unavailable
The upstream Maven search service is not available.
HTTP Status: 503
Help Links:
SHA1 Not Found
Unable to find the coordinates for the provided SHA1.
HTTP Status: 404
Help Links:
Your organisation is not authorised to perform this action
You likely don’t have access to the Beta. To get access, you can request access to the Beta through your account manager or team.
HTTP Status: 403
Authorization request failure
Unexpected error when authenticating. Please try again, and if you continue to experience issues please contact support.
HTTP Status: 500
Invalid PURL has been provided
Please make sure that the purl you’ve provided is valid. Please see the Package URL specification link for further information.
HTTP Status: 400
Help Links:
Ensure you specify a namespace in the purl and then try again
You have requested a package type which requires a namespace (eg. maven group id). Please supply the namespace in order to retrieve the package correctly.
HTTP Status: 400
Help Links:
Ecosystem is not supported
Ensure that the package type is a supported type.
HTTP Status: 400
Purl components required
Currently we require a list of components of the package url specification. The purl supplied by the user did not specify all the components which we currently require.
HTTP Status: 400
You have submitted a purl with components which are not supported
Please remove the component which is not supported, and try to make the request again. The endpoint only accepts particular components.
HTTP Status: 400
Requested package not found
The package you’ve specified in the purl can not be found in our vulnerability database. Please check that the package name, ecosystem and version are correct and then try again.
HTTP Status: 404
Vulnerability service is currently not available
This issue is unexpected, and the service should recover quickly. If not, please contact support.
HTTP Status: 503
This issue is unexpected and the service should recover quickly if not please contact support
An unexpected error occurred. Please try again, and if you continue to experience issues please contact support.
HTTP Status: 500
This issue is unexpected and the service should recover quickly if not please contact support
An unexpected error occurred with the vulnerability service. Please try again, and if you continue to experience issues please contact support.
HTTP Status: 500
An error was experienced by the service when processing the request
This issue is unexpected, and the service should recover quickly. If not, please contact support.
HTTP Status: 500
Invalid pagination parameters
Please ensure the supplied pagination limit is > 1 and <= 1000, and that the offset is >= 0.
HTTP Status: 400
Purls provided exceeds limit
The number of purls sent in the request exceeds the limit set by the service.
HTTP Status: 400
Number of issues exceeds limit
The number of issues found for the provided purls exceeds the limit defined by the API. You may attempt to resolve this by reducing the number of purls you send in a single request.
HTTP Status: 400
Expected distro to be present
The given Package URL does not have a required distro qualifier.
HTTP Status: 400
Unsupported Debian distro
This Debian distro is not currently supported.
HTTP Status: 400
Expected namespace to be present
The given Package URL does not have a required namespace.
HTTP Status: 400
Vendor not supported
The given Package URL does not contain a supported vendor.
HTTP Status: 400
OpenSourceProjectIssues
Invalid request
Please check the body of your request and try again.
HTTP Status: 400
Unable to return valid API response
This should resolve, however please contact support if you continue to experience issues.
HTTP Status: 500
Failed to process data
This should resolve, however please contact support if you continue to experience issues.
HTTP Status: 500
Failed to store issue data
Please check your inputs and try again. If you continue to experience issues please contact support.
HTTP Status: 500
Internal server error
This issue is unexpected, and the service should recover quickly. If not, please contact support.
HTTP Status: 500
Open Source Project Snapshots
Invalid request
Please check the body of your request and try again.
HTTP Status: 400
Unable to return valid API response
This should resolve, however please contact support if you continue to experience issues.
HTTP Status: 500
Failed to process data
This should resolve, however please contact support if you continue to experience issues.
HTTP Status: 500
Failed to store snapshot data
Please check your inputs and try again. If you continue to experience issues please contact support.
HTTP Status: 500
Internal server error
This issue is unexpected, and the service should recover quickly. If not, please contact support.
HTTP Status: 500
Generated at 2023-05-08T07:22:22.200Z
Last updated
Was this helpful?