An improvement has been made to Continuous Dynamic AutoAPI. When adding endpoints for an API asset, all endpoints are now enabled for scanning by default. Previously, endpoints with POST, PUT, PATCH, or DELETE HTTP methods had to be enabled individually. This change applies when uploading an API specification document or adding endpoints individually.

The following legacy API endpoints have been deprecated:

New functionality to list all the roles associated with a given user has been added to the following API endpoints:

The IP address ranges for WhiteHat Dynamic scanning services have been updated. The following IP addresses are no longer required:

The WhiteHat Dynamic scanning services IP address ranges have been updated. The following IP addresses are no longer required:

The notes field has been deprecated and is now removed from /api/apiAssets/{siteID}, and /api/v2/sites/{siteID}.

A new API has been added, /api/scanStats, to the Site API v2.0. This API helps users monitor deviations in the number of links found in a scan. The threshold is configurable as a parameter. Previously, customers would have to monitor this data from each completed scan manually in order to check trends and anomalies.

The WhiteHat Dynamic scanning services IP address ranges have been updated, with the following additions.
EU Customers
3.72.175.49
3.76.244.88
18.194.206.33
Non-EU Customers
162.223.124.132
162.223.124.135
The Sentinel help documentation has been updated to reflect this change.
https://source.whitehatsec.com/help/sentinel/whitehat-ip-ranges-snpt.html
https://source.whitehatsec.com/help/sentinel/production-safety.html

Per users' feedback, we are reverting a behavior change introduced to the Site API v1.0 on Apr 28, 2023. Previously, the password was required whenever adding or modifying Site Credentials. The password is still required for adding a credential, but is no longer required for modifying a credential. The public API documentation has been updated to reflect this change.

All Asset API v1.0 requests will now return a deprecation warning response header. While the asset requests are still functional, users should shift to using the Asset API v2.0 as soon as possible.