The Tenable.io Web Application Scanning v2 API now supports HTML and PDF scan exports. The HTML and PDF exports contain the list of targets, scan results, and scan notes.

The Tenable.io Web Application Scanning v2 API now supports email notifications upon scan completion. You can configure email notifications when you create a scan configuration. Email notifications are sent upon scan completion for both on-demand and scheduled scans.

The default behavior for vulnerability exports has changed. By default, vulnerability exports will now only include vulnerabilities found or fixed within the last 30 days if no time-based filters (last_fixed, last_found, or first_found) are submitted with the request. Previously, the default behavior was all vulnerabilities since Unix epoch time.

Tenable recommends the use of a standard User-Agent string in request headers when building integrations with the Tenable.io API. A standard User-Agent string helps Tenable to identify your integrations and API calls, and it assists in debugging and troubleshooting if you have issues with the API, rate limits, or concurrency limits.

The Web Application Scanning v2 API now returns more specific error messages when validating user input. The new error model helps users to quickly identify and correct input errors.

Two new asset filters were added to the Tenable.io API to help filter deleted and terminated assets. The new filters are is_deleted and is_terminated. If these filters are set to true, the Tenable.io API will return all assets that have been deleted or terminated.

The Web Application Scanning v2 API has been updated to make targets a primary entity. You can now define target in the main body of your request instead of within the settings object. This change allows users to create a scan configuration with no settings block if they wish to use the default settings. Tenable recommends that you use the target parameter in the main body instead. This change affects the POST /was/v2/configs and PUT /was/v2/configs/{config_id} endpoints.

With scan routing, you can automatically dispatch scanning across multiple scanner groups according to the areas of your network that each group is configured to access. Scan routing reduces scan configuration and management overhead by eliminating the need to configure specific scanners for each individual scan. This feature can represent a significant benefit in large deployments. In addition, you can improve operational efficiency by tasking higher-privilege team members with managing scanner pools, which lower-privilege team members can then use in scan configuration.

Documentation is now available for the GET /plugins/plugin endpoint. This endpoint returns a paginated list of Tenable plugins with detailed plugin information. The response list is sorted by plugin ID.

The Tenable.io export API now returns the Asset Criticality Rating (ACR) and Asset Exposure Score (AES) if you have a Lumin license. The GET /assets/export/{export_uuid}/chunks/{chunk_id} endpoint returns the following attributes: