DevOps
Learn how to extend the product with REST APIs and plugins.
- REST API
  Learn about REST API in AppScan Enterprise.
  - AppScan Enterprise REST APIs
  - Defect Tracking System Integration REST API
    Learn how to use built-in Defect Tracking System Integration REST API interface to visualize RESTful web services that are used for submitting defects.
  - Scan Management REST APIs (Legacy)
    - AppScan Enterprise REST web services
      Use an Application Programming Interface (API) through REST web services to perform a variety of tasks, particularly providing access to reporting data.
      - Using services through Liberty authentication
        Learn how to use services through Liberty authentication.
      - Error handling
        When a REST service returns data, it normally returns a 200 OK HTTP status along with the returned XML data.
      - Long running tasks
        Some tasks might take a long time to run on the server. In this case, they might need to run beyond the allotted timeout period on the server.
    - Sample 1: Creating and running a scan using AppScan Enterprise REST API
      This sample leads you through creating and running a scan.
    - Sample 2: DAST Scanning through Build Automation
    - Services
      These REST web services perform a variety of tasks, particularly providing access to reporting data.
  - API change history
    Track changes made to the REST APIs across product versions.
- Plugins and integrations

AppScan Enterprise REST web services

Use an Application Programming Interface (API) through REST web services to perform a variety of tasks, particularly providing access to reporting data.

These services use HTTP (GET and POST). Each service is of the form

https://<server>/<instance>/services/<service>

For example, performing an HTTP GET on

https://localhost/ASE/services/version

requests version information about the AppScan® Enterprise server.

When a service requires a parameter, such as

/services/folders/<fid>

substitute the parameter with an actual ID. For example,

https://localhost/ASE/services/folders/1

Data is sent and received in XML format, conforming to the schema which can be downloaded using the service

https://<server>/<instance>/services/schema.

Note: Each service will return data in the language specified by the authenticated user's settings. These settings can be accessed via the web UI.