Get Logging for a Specific Device:

`GET /logging/{acc}/devices/{deviceId}/logs`

Gets logs for a specific device.

Uses and Requirements

(are there specific types of logTypes and eventLogs?)

Request Components

HTTP Request

GET https://thingspace.verizon.com/api/fota/v2/logging/{acc}/device/(deviceId}/logs)

Resource Path Parameters

You must include the account name and the deviceId in the path.

Parameter Name	Data Type	Description
acc required	string	The name of the account for which you want to disable logging. An account name is usually numeric, and must include any leading zeros.
deviceId required	string	The device IMEI identifier.

Header Parameters

The request header must contain a current ThingSpace authorization token and a current VZ-M2M-session token.

Parameter Name	Data Type	Description
Authorization required	string	HTTP Authorization request header containing a valid Bearer token.
VZ-M2M-Token required	string	A valid session token returned by a Connectivity Management POST /session/login request.

Request Body

None

Example Request

Disable logging for a specific devices:

curl -X DELETE https://thingspace.verizon.com/api/fota/v2/logging/$ACC/devices/$DEVICEID  -H 'Authorization: Bearer $AUTH_TOKEN' -H 'VZ-M2M-Token: $M2M_TOKEN'

Success Responses

Status 200

A success response contains a list of device logs.

Example Success Response

[
  {
    "deviceId": "990013907835573",
    "logTime": "2020-10-22T19:29:50.901Z",
    "logType": "string",
    "eventLog": "string",
    "binaryLogFileBase64": "string",
    "binaryLogFilename": "string"
  }
]

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.