The PUT and POST methods for User API v1.0 has been updated. The fields 'first name' and 'last name' now have character limits of twenty and fifty, respectively. This change aligns the behaviour of the APIs and the Sentinel UI.

A new parameter option has been added to the Site API v1.0. The satellite_id parameter has been added to the Modify a site PUT request, this allows a requester with the correct privileges to change the Appliance used for scanning a Site. The Satellite ID provided must be for a valid DAST Appliance on the Site’s client.  

Sentinel APIs will now only accept authentication of API keys in the Request Headers as mentioned in the Using an API Key in Request Headers section in Authentication. If Sentinel APIs are called with API key in the URI as a query parameter a 401 status code will be returned. 

Effective June 30, 2022, Sentinel APIs will only accept authentication of API key in the Request Headers as mentioned in the section Using an API Key in Request Headers in Authentication. If Sentinel APIs are called with API key in the URI as a query parameter after June 30, 2022, a 401 status code will be returned. 

A fix has been provided for the Site API v1.0. Previously, when using the Site API v1.0 to access the site’s credential page, Sentinel would return a 500 error. An update to the Sentinel Database has been implemented to address this error. This issue has now been fixed. 

An existing parameter has been removed from the Sites API v2.0. The scanShedule parameter has been removed from the POST request, which removes the option to add a scan schedule during site provisioning. The API documentation has been updated to reflect this change. 

Effective February 15, 2022, Sentinel APIs will only accept authentication of API key in the Request Headers as mentioned in the section Using an API Key in Request Headers. If Sentinel APIs are called with API key in the URI as a query parameter after February 15, 2022, a 401 status code will be returned. 

Effective January 31, 2022, Sentinel APIs will only accept authentication of API key in the Request Headers as mentioned in the section Using an API Key in Request Headers. If Sentinel APIs are called with API key in the URI as a query parameter after January 31, 2022, a 401 status code will be returned. 

A new parameter option has been added to the Findings API v2.0 and the API documentation has been updated to reflect this. The new parameter option is called descAndSolution and can be defined in the fields parameter. Using the new parameter option, users can now fetch a description and solution for their findings.

Effective January 31, 2022, Sentinel APIs will only accept authentication of API key in the Request Headers as mentioned in the section Using an API Key in Request Headers in https://apidocs.whitehatsec.com/whs/docs/authentication. If Sentinel APIs are called with API key in the URI as a query parameter after January 31, 2022, a 401 status code will be returned.