Skip to main content

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 callDescriptionXML API parametersScan type
detailedreport.do

REST equivalent:
GET /appsec/v2/applications/{application_guid}/findings
Compiles a detailed report for the specified application build.build_idStatic,
Dynamic,
Manual
detailedreportpdf.doProduces a PDF file of the detailed report for the application build.build_idStatic,
Dynamic,
Manual
getaccountcustomfieldlist.do

REST equivalent:
GET /appsec/v1/custom_fields
Returns the ID and name of the available custom fields in use by the organization of the user. Static,
Dynamic,
Manual
getappbuilds.do

REST equivalent:
GET /appsec/v1/applications with the Findings API
Compiles a detailed list of applications and statuses, including all application and build profile data.

Optional:
only_latest
report_changed_since
Static,
Dynamic,
Manual
getcallstacks.do

REST equivalent:
GET /appsec/v2/applications/{application_guid}/findings/{issue_id}/static_flaw_info
Retrieves the call stacks for a static flaw.build_id
flaw_id
Static
summaryreport.do

REST equivalent:
GET /appsec/v2/applications/{application_guid}/summary_report
Compiles a summary XML report for the specified application build.build_idStatic,
Dynamic,
Manual
summaryreportpdf.doProduces a PDF file of the summary report for the specified application build.build_idStatic,
Dynamic,
Manual
thirdpartyreportpdf.doProduces a PDF file of the scan results for a third-party application.build_idStatic,
Dynamic,
Manual