Learn how to extend the product with REST APIs and plugins.
Learn about REST API in AppScan Enterprise.
These REST web services perform a variety of tasks, particularly providing access to reporting data.
Learn about using this REST service to retrieve scan related information.
Learn how to use built-in Defect Tracking System Integration REST API interface to visualize RESTful web services that are used for submitting defects.
Use an Application Programming Interface (API) through REST web services to perform a variety of tasks, particularly providing access to reporting data.
This sample leads you through creating and running a scan.
This REST service will return the web services schema. The schema is fully annotated to describe the elements and attributes returned by all web services. Please refer to this document regarding XML specifics.
This REST service will return version information about the Server.
Learn about using this REST service to get <folder> elements.
This REST service will retrieve a list of available job templates that you have access to in the Templates directory or any of its sub-folders..
This REST service will retrieve scanlogs from the Log directory for a Scan.
This REST service will retrieve statistics of a scan.
This REST service will create a scan job and an associated report pack based on a specific template. The name and description fields are supplied to the server using POST data.
This REST service will configure content scan job options, such as adding a Starting URL.
This REST service will update the action (start scan, suspend, cancel, end, resume) of a folder item (job, report pack, dashboard).
This REST service will upload the manual explore data that is stored in an *.htd / *.har / *.dast.config file to AppScan® Enterprise. The size of the traffic file should not exceed 20 MB. If you exceed this limit, split the file into smaller chunks by recording smaller sequences. To use the files in *.har or *.dast.config file formats, an additional parameter format is to be passed into the request. Examples are provided below.
This REST service will set the user credentials to log in to a website that uses Basic or NTLM authentication. The password is encoded before it is saved in the database, but it is received in clear text. Call this REST service over HTTPS and use a test user account during the manual explore to prevent usernames and passwords from appearing in clear text in the Enterprise Console interface.
This REST service uploads the manual explore data that is stored in an *.htd / *.har / *.dast.config file as a recorded login sequence to a content scan job, and sets the Login Method for the content scan job to "Recorded Login".
Learn about using this REST service to get report results.
Track changes made to the REST APIs across product versions.