Disable logging for a list of devices
DELETE /logging/{accountName}/devices
Disables logging for specified devices.
Uses and Requirements
Logging automatically turns off on a device after 7 days, but if you want to disable logging before then, you can disable logging for a device or list of devices.
HTTP Request
DELETE https://thingspace.verizon.com/api/fota/v2/logging/{accountName}/devices
Resource Path Parameters
You must include the account name in the path.
| Parameter Name | Data Type | Description |
|---|---|---|
| accountName required | string | The name of the account for which you want the list of devices. An account name is usually numeric, and must include any leading zeros. |
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 | HTTP Authorization bearer token: Authorization: Bearer {token} |
| VZ-M2M-Token required | string | A valid session token: VZ-M2M-Token: {M2Mtoken} |
Request Body
| Parameter Name | Data Type | Description |
|---|---|---|
| deviceLogging | array of deviceIds objects | The list of device ids for which you want to disable logging. |
| deviceIds | string | List of device IMEI identifiers. |
Example Request
Disable logging for devices:
curl -X DELETE https://thingspace.verizon.com/api/fota/v2/logging/$ACC/devices -H 'Authorization: Bearer $AUTH_TOKEN' -H 'VZ-M2M-Token: $M2M_TOKEN' -d
'{
deviceIds: [
"990013907835573",
"991124018926684",
"992234129057795",
"998891785613351",
"990013907835573"
]
}'Success Responses
Status 200
A success response contains the 200 code as confirmation of disabling logging for the specified devices.
Example Success Response
{
"success": true
}Failure Responses
Status 400
All error messages are returned in this format:
{
"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