Get a list of devices with logging enabled
GET /logging/{accountName}/devices
Returns an array of all devices in the specified account for which logging is enabled.
Uses and Requirements
Each response includes a maximum of 20 devices because you can only enable logging for a maximum of 20 devices.
HTTP Request
GET 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
None.
Example Request
Request the list of logging-enabled devices for an account:
curl https://thingspace.verizon.com/api/fota/v2/logging/$ACC/devices -H 'Authorization: Bearer $AUTH_TOKEN' -H 'VZ-M2M-Token: $M2M_TOKEN'Success Responses
Status 200
A success response contains the account name and an array of device objects.
| Parameter Name | Data Type | Description |
|---|---|---|
| deviceId | string | The IMEI of the device. |
| expiryDate | string($date) | The date when device logging expires. |
Example Success Response
[
{
"deviceId": "990013907835573",
"expiryDate": "2020-10-19"
},
{
"deviceId": "991124018926684",
"expiryDate": "2020-10-19"
},
{
"deviceId": "992234129057795",
"expiryDate": "2020-10-23"
},
{
"deviceId": "998891785613351",
"expiryDate": "2020-10-23"
},
{
"deviceId": "990013907835573",
"expiryDate": "2020-10-23"
}
]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.