Results XML APIs Quick Reference
This table lists the XML API calls for managing scan results. For more detailed information, see the topic for a specific call.
Veracode strongly recommends that you use the REST APIs. For new integrations, always use the REST APIs.
XML API Call | Description | Required Parameters | Optional Parameters | Scan Type | Equivalent REST API Call |
---|---|---|---|---|---|
detailedreport.do | Compiles a detailed report for the specified application build. | build_id | Static, Dynamic, Manual | GET /appsec/v2/applications/{application_guid}/findings | |
detailedreportpdf.do | Produces a PDF file of the detailed report for the application build. | build_id | Static, Dynamic, Manual | ||
getaccountcustomfieldlist.do | Returns the ID and name of the available custom fields in use by the organization of the user. | Static, Dynamic, Manual | GET /appsec/v1/custom_fields | ||
getappbuilds.do | Compiles a detailed list of applications and statuses, including all application and build profile data. | only_latest , report_changed_since | Static, Dynamic, Manual | GET /appsec/v1/applications with the Findings API | |
getcallstacks.do | Retrieves the call stacks for a static flaw. | build_id , flaw_id | Static | GET /appsec/v2/applications/{application_guid}/findings/{issue_id}/static_flaw_info | |
summaryreport.do | Compiles a summary XML report for the specified application build. | build_id | Static, Dynamic, Manual | GET /appsec/v2/applications/{application_guid}/summary_report | |
summaryreportpdf.do | Produces a PDF file of the summary report for the specified application build. | build_id | Static, Dynamic, Manual | ||
thirdpartyreportpdf.do | Produces a PDF file of the scan results for a third-party application. | build_id | Static, Dynamic, Manual |