About API roles
This section describes the non-API user roles that your user account must have before you can use the APIs to automate specific tasks.
If you are a member of a team, the access of the team to specific accounts also determines your permissions.
To use the Upload, Results, and Mitigation and Comments APIs, you must select one of these checkboxes:
- API Service Account checkbox and the respective API user role
- The respective non-API user roles (user account), such as Reviewer or Security Lead
Archer Report API
API role | User account role | Tasks |
---|---|---|
Archer Report | Submitter |
|
Admin API
If you intend to use the Admin API to create a new user account, you must pass the role parameters and the scan type permissions.
The role parameters for the user account are case-sensitive.
The user role parameters are:
- Administrator
- Creator
- Executive
- Mitigation Approver
- Policy Administrator
- Reviewer
- Security Lead
- Submitter
- Security Insights
- eLearning
The scan permission types are:
- Static Scan
- Dynamic Scan
- Manual Scan
- All Scan Types
When the visibility for an application is set 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.
API role | User account role | Tasks |
---|---|---|
Admin | Security Lead, Creator, or Submitter, depending on the task you want to perform. |
|
Greenlight API
The Greenlight API User role is only available to organizations with active Veracode Greenlight subscriptions.
API role | User account role | Tasks |
---|---|---|
Greenlight API User | Greenlight IDE User |
|
Mitigation and Comments API
API role | User account role | Tasks |
---|---|---|
Mitigation | Reviewer or Security Lead |
|
Results API
API role | User account role | Tasks |
---|---|---|
Results | Reviewer or Security Lead |
|
Reporting API
API role | User account role | Tasks |
---|---|---|
Reporting | Security Lead, Executive, or Security Insights |
|
Upload and Scan API
API role | User account role | Tasks |
---|---|---|
Upload and Scan | Security Lead, Creator, or Submitter, depending on the task you want to perform. A user with the Creator role can only create application profiles for teams in which the Creator is a member. The Submitter role can submit a scan request. The Security Lead role can perform all tasks. API users need the Upload and Scan API role to create a new application using Veracode Static for Visual Studio and to create sandboxes using the Veracode Jenkins Plugin. |
|
Upload API - Submit Only
This role can also create and delete scan requests, and has the ability to edit builds before rescanning the application. However, this role does not allow users to create new applications, including users of the Veracode integrations.
API role | User account role | Tasks |
---|---|---|
Upload - Submit only | Submitter |
|