The Veracode REST and XML APIs mirror the main tasks for scanning applications, reviewing results, mitigating findings, and administrating your organization in the Veracode Platform. Veracode strongly recommends that you use the REST APIs. For new integrations, always use the REST APIs.
To understand how the APIs work, Veracode recommends that you familiarize yourself with the Veracode Platform workflow for scanning applications first, before beginning to use the APIs. You also should be familiar with how APIs function.
Veracode APIs are designed for members of a software development team responsible for performing security checks on software code. They enable developers who work in rapid build-and-test cycles to fully automate security verification for entire software portfolios, and to integrate with internal build and bug-tracking systems. Instead of manually using the Veracode Platform to go through the individual steps of configuring and submitting a scan request and, then, reviewing the results, you can integrate the API calls directly into your IDE and build system code to scan early and often.
To test the security of your API specifications, see Getting Started with Veracode API Scanning.
Veracode REST APIs
The Veracode REST APIs follow the OpenAPI industry standard specification. These APIs return JSON instead of XML, and require authentication using HMAC. See Using the Veracode REST APIs. The Veracode REST APIs require Veracode API credentials.
Veracode XML APIs
The Veracode XML APIs are web APIs, each having a defined set of HTTP request messages that return structured response messages in XML. See Using the Veracode XML APIs.
Veracode reserves the right to apply API rate limiting to any account that exceeds the allowed number of API requests within a specific period.