To be able to access the Veracode APIs, you must have a Veracode account with the required roles for performing specific tasks with the APIs.
Ensure 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.
You must have the Administrator or Team Admin role to create API service accounts. You configure API user roles and permissions on the User Account page in the Veracode Platform. To use the Admin or Archer Report XML APIs, you must have the API Service Account checkbox selected (API service account) and the respective API user roles selected in the Login Settings section of the User Account page in the Veracode Platform. You can also assign roles with the Identity REST API or the Admin XML API.
You can restrict API service accounts to teams, limiting their access to only data for applications that are associated with that team. Select Restrict to Selected Teams, then choose the appropriate team. You can also restrict the scan types a user can perform.
If you want to create a new user account with the APIs, you must pass both the role parameters and the scan type permissions. For a user account, the role parameters (case-sensitive) are:
The scan permission types are:
All Scan Types
Team Administrators can grant only these API roles to users they manage: Results API, Upload and Scan API, Mitigation API, Upload API - Submit Only, and Greenlight API.
If you set the visibility for an application to Teams & Security Leads, before a user account can access the application using the Veracode APIs, that account must have the Reviewer, Creator, or Submitter user roles and be a member of the specified team.