Delete a Trigger
# Delete a Trigger ### `DELETE /v1/triggers/{triggerId}` Delete a specified trigger. ## HTTP Request DELETE [https://thingspace.verizon.com/api/m2m/v1/triggers/{triggerId}](/docs/premium-apis/thingspace-intelligence/api-endpoints/anomaly-triggers/deleteanomalydetectiontrigger) ## Resource and Query Parameters You must specify the trigger that you want to delete in the resource path. | Parameter Name | Data Type | Description | |:--------------|:---------|:---------------------------------------| | **triggerId** <br> _required_ | string | The unique ID of the trigger that you want to delete. | ## Header Parameters The request header must contain a current ThingSpace authorization bearer token and a valid VZ-M2M session token, and must set the content-type to JSON. 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 The response contains the ID of the trigger that was deleted. | Parameter Name | Data Type | Description | |:--------------|:---------|:---------------------------------------| | **triggerId** | string | The ID of the trigger that was deleted. | ### Example Success Response ``` json { "triggerId": "595f5c44-c31c-4552-8670-020a1545a84d", } ``` ## Failure Responses Status 400 All error messages are returned in this format: ``` json { "errorCode": "error code string", "errorMessage": "error message string" } ``` Error codes and messages are listed on the Error Messages page, along with explanations and suggestions for corrective actions.