Delete Usage Trigger
Delete a Usage Trigger
DELETE /usage/accounts/{accountName}/triggers/{triggerId}
Delete a specified trigger.
Uses and Requirements
Note: This method uses the /subsc/v1 basepath, not /loc/v1 used by other Device Location API requests.
HTTP Request
DELETE https://thingspace.verizon.com/api/subsc/v1/usage/accounts/{accountName}/triggers/{triggerId}
Resource Path and Query Parameters
You must include the account name and the unique ID of the trigger that you want to delete in the path.
| Parameter Name | Data Type | Description |
|---|---|---|
| accountName (required) | string | The name of the billing account in the format of 10 digits, a hyphen, and then five more digits. Must include any leading zeros. |
| triggerId (required) | string | The unique ID of the trigger to delete. The ID was returned in the response when the trigger was created, and you can also find it in the GET /triggers response. |
Header Parameters
The request header must 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.
| Parameter Name | Data Type | Description |
|---|---|---|
| Authorization (required) | string | HHTTP Authorization bearer token: Authorization: Bearer {token}. |
| VZ-M2M-Token (required) | string | A valid session token returned by POST /api/m2m/v1/session/login using the primary account’s credentials. |
| Content-Type (required) | string | Must be application/json: Content-Type: application/json. |
Request Body
None.
Success Responses
Status 200
A success response contains the confirmation of the trigger deletion.
Failure Responses
All error messages are returned in this format:
{
"errorCode": "The 3-digit HTML error code",
"errorMessage": "string"
}Error codes and messages are listed on the Error Codes page, along with explanations and suggestions for corrective actions.