getcallstacks.do

Veracode APIs

The getcallstacks.do call retrieves the call stacks for a specified flaw in a specific build.

Before using this API, Veracode strongly recommends that you read API Usage and Access Guidelines.

REST API Equivalent

The REST API equivalent of this call is a GET to /appsec/v1/custom_fields using the Findings API. Veracode strongly recommends that you use the REST API for this action. For new integrations, always use the REST APIs.

Resource URL

https://analysiscenter.veracode.com/api/5.0/getcallstacks.do

Parameters

Name Type Description
build_id

Required

Integer Application or sandbox build ID.
flaw_id

Required

Integer To find flaw_id values, look for issueid fields in the detailed XML report.
Note: This call returns detailed flaw data only available for internally developed applications. Using this call for a third-party application returns an error.

HTTPie Example

Examples use the HTTPie command-line tool. See Using HTTPie with the Python Authentication Library.

http --auth-type=veracode_hmac "https://analysiscenter.veracode.com/api/5.0/getcallstacks.do" "build_id==<build_id>" "flaw_id==13"

HTTPie Results

The getcallstacks.do call returns the callstacks_<app_id>_<build_id>_<flaw_id> XML document, which references the callstacks.xsd. schema file. You can use the XSD schema file to validate the XML data.
<?xml version="1.0" encoding="UTF-8"?>

<callstacks xmlns:xsi="http&#x3a;&#x2f;&#x2f;www.w3.org&#x2f;2001&#x2f;XMLSchema-instance" 
            xmlns="https&#x3a;&#x2f;&#x2f;analysiscenter.veracode.com&#x2f;schema&#x2f;2.0&#x2f;callstacks" 
            xsi:schemaLocation="https&#x3a;&#x2f;&#x2f;analysiscenter.veracode.com&#x2f;schema&#x2f;2.0&#x2f;callstacks 
            https&#x3a;&#x2f;&#x2f;analysiscenter.veracode.com&#x2f;resource&#x2f;2.0&#x2f;callstacks.xsd" 
            callstacks_version="1.1" build_id="4722563" flaw_id="13">
   <callstack module_name="app_web_commentview.ascx.cd7a1e1e.dll" steps="1" local_path="documents and settings&#x2f;
            tjones#x2f;my documents&#x2f;demo&#x2f;blogenginedotnet&#x2f;1.3&#x2f;blogengine.web&#x2f;themes&#x2f;
            python-demo&#x2f;commentview.ascx" function_name="__Render__control1" line_number="8">
      <call data_path="1" file_name="commentview.ascx" file_path="documents and settings&#x2f;tjones#x2f;my documents&#x2f;
            demo&#x2f;blogenginedotnet&#x2f;1.3&#x2f;blogengine.web&#x2f;themes&#x2f;python-demo&#x2f;commentview.ascx" 
            function_name="__Render__control1" line_number="8"/>
   </callstack>
</callstacks>

API Wrapper Examples

Java example:

java -jar vosp-api-wrapper-java{version}.jar -vid <Veracode API ID> -vkey <Veracode API Key> -action getcallstacks -buildid <build id> -flawid 13

C# example:

VeracodeC#API -vid <Veracode API ID> -vkey <Veracode API key> -action getcallstacks -buildid <build id> -flawid 13

API Wrapper Results

The getcallstacks.do call returns the callstacks_<app_id>_<build_id>_<flaw_id> XML document, which references the callstacks.xsd. schema file. You can use the XSD schema file to validate the XML data.

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
        
        <callstacks xmlns="https://analysiscenter.veracode.com/schema/2.0/callstacks" 
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" build_id="<build id>" 
        callstacks_version="1.1" flaw_id="13" 
        xsi:schemaLocation="https://analysiscenter.veracode.com/schema/2.0/callstacks 
        https://analysiscenter.veracode.com/resource/2.0/callstacks.xsd">
        <callstack function_name="__Render__control1" line_number="8" 
        local_path="documents and settings/juno/my 
        documents/demo/blogenginedotnet/1.3/blogengine.web/themes/barks/commentview.ascx" 
        module_name="app_web_commentview.ascx.cd7a1e1e.dll" steps="1">
        <call data_path="1" file_name="commentview.ascx" file_path="documents and settings/juno/my 
        documents/demo/blogenginedotnet/1.3/blogengine.web/themes/barks/commentview.ascx" 
        function_name="__Render__control1" line_number="8"/>
        </callstack>
        </callstacks>