Troubleshooting APIs and Wrappers
This section helps you remedy common problems and understand how better to use Veracode APIs and wrappers.
|API or Wrapper||Issue||Solution|
|Any API or Wrapper||I received an HTTP 401 or Access Denied error. I do not have access to the APIs or I am unsure what kind of access I need.|
You must have a Veracode account with the required API roles assigned by your Veracode administrator.
Ensure your Veracode API credentials are valid and have not expired. You can generate new credentials in the Veracode Platform.
|Any API||I cannot log in to Veracode when using the APIs.||Veracode APIs and integrations require access to |
Verify that your IP address is in the list or range of addresses in the Allowed IP Addresses field of your user account login settings. If the IP range is set incorrectly, edit the Allowed IP Addresses field to include the IP address of the location of your login.
|Any API||The scan stopped after prescan.||To determine why a scan that started from an API failed after prescan, review the response code returned from |
|Any API||I received cURL error 35.||If you receive the cURL error |
|Any Wrapper||I received a message that displays missing mandatory parameters.||Provide all mandatory parameters in your call. If you do not provide all mandatory parameters, the wrapper returns the missing mandatory parameters in your console.|
|Any Wrapper||I cannot connect to Veracode through my proxy.||If your organization uses a proxy for outbound connections, provide this information to the wrapper to successfully connect to Veracode.|
|Archer API||See Troubleshooting GRC Integrations.|
|Dynamic Analysis API||I need to open a support case with Veracode Technical Support.||Provide this information to Veracode Technical Support: |
|Java API Wrapper or Veracode Jenkins Plugin||See Troubleshooting Build and Release Management System Integrations|
|Java API Wrapper||I experience a ||Add these lines to the |
|Flaw Report API||I see HTTPS status code ||If you try to call |
|Results API||The ||Veracode recommends that you use |
|Upload API||I do not know if the prescan is complete or successful.||To check the prescan results in the Upload API, call |
|Upload API||My scan does not complete due to non-fatal errors.||If you want to ensure the scan completes even though there are non-fatal errors such as unsupported frameworks, ensure you use the |
|Upload API and Integrations||I received a fatal error after prescan, which is preventing my static analysis from starting automatically.||Before the next time your static analysis is scheduled to start automatically, you need to:|
|Any Plugin, Any API||When using either a Veracode plugin, the Veracode API wrappers, or a custom script, I see this returned in the output text: ||This message indicates that a previous static scan did not succeed for the specific application. Log into the Veracode Platform and review the application's current scans to determine if the previous scan did not successfully complete. A previous scan may still be in progress. If a previous scan is still running due to an error, select Delete. You can then use the plugin to submit a new scan request.|
|Any Plugin, Any API||I receive an error when an API or integration attempts to access Veracode.||Veracode APIs and integrations require access to |