Skip to main content

The call returns the ID and name of the available custom fields for your organization. You must have the Results API role to be able to use this API.

Before using this API, Veracode strongly recommends that you read API usage and access guidelines. Ensure you access the APIs with the domain for your region.

REST API equivalent

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


There is no equivalent API wrapper call for

Resource URL


This call takes no parameters.

HTTPie example

Examples use the HTTPie command-line tool.

http --auth-type=veracode_hmac ""

HTTPie results

The call returns the accountcustomfieldlist XML document, which references the accountcustomfieldlist.xsd schema file. You can use the XSD schema file to validate the XML data.

<?xml version="1.0" encoding="UTF-8"?>

<account_customfieldlist xmlns:xsi="http&#x3a;&#x2f;&#x2f;;2001&#x2f;XMLSchema-instance"
<account_customfield id="132422" name="Custom 1"/>
<account_customfield id="132423" name="Custom 2"/>
<account_customfield id="132424" name="Custom 3"/>
<account_customfield id="132425" name="Custom 4"/>
<account_customfield id="132426" name="Custom 5"/>
<account_customfield id="132427" name="Custom 6"/>
<account_customfield id="132428" name="Custom 7"/>
<account_customfield id="132429" name="Custom 8"/>
<account_customfield id="132430" name="Custom 9"/>
<account_customfield id="132431" name="Custom 10"/>