Reset Anomaly Detection Parameters
# Reset Anomaly Detection Parameters ### `PUT /intelligence/{accountName}/anomaly/settings/reset` Resets the Anomaly Detection thresholds for an account ID. Thresholds are reset to Zero. ## HTTP Request PUT [https://thingspace.verizon.com/api/m2m/v1/intelligence/{accountName}/anomaly/settings/reset](/docs/premium-apis/thingspace-intelligence/api-endpoints/anomaly-settings/resetanomalydetectionparameters) ## Resource Path and Query Parameters | Parameter Name | Data Type | Description | |:---------------------|:---------|:------------------------------------------------------------------------------------------------------| | **accountName** <br> _required_ | string | The name of a billing account. An account name is usually numeric, and must include any leading zeros. | ## Header Parameters The request header must set the content-type to JSON, contain a current ThingSpace authorization token and a current VZ-M2M session token. For more details on how to get these tokens, visit [Getting Started](https://thingspace.verizon.com/documentation/api-documentation.html#/http/session-management/guides/getting-started). | Parameter Name | Data Type | Description | |:-----------------------|:-----------|:-----------------------------------------------------------------------------| | **Authorization** <br> _required_ | string | HTTP Authorization bearer token: <br> `Authorization: Bearer {token}` | | **VZ-M2M-Token** <br> _required_ | string | A valid session token: <br> `VZ-M2M-Token: {M2Mtoken}` | | **Content-Type** <br> _required_ | string | Must be application/json: <br> `Content-Type: application/json` | ## Request Body None. ## Success Responses Status 200 ``` json { "status": "Success" } ``` ## Failure Responses Status 400 All error messages are returned in this format: ``` json { "errorCode": "error code string", "errorMessage": "error message string" } ```