This document outlines the changes to the BitBrew platform, management API, and Dashboard application that will be released Jul 22, 2019. Changes should be carefully read and understood.

Table of Contents

  • Oauth endpoint brought into spec

  • New field in Device File Status and History responses

Oauth Endpoint Brought Into Spec

The refresh_token field has been removed from the response because it is prohibited by the Oauth2 specification.

POST /v1/oauth/token

Response 200

{
"access_token": "ZDIwYTc4YmUtMzQ3My00NzUyLTkyYzItYzBhYWEyODgwZGMx",
"expires_in": 3599,
"token_type": "Bearer"
}

New Field in Device File Status Response

A new field called lastModifiedAt provides a timestamp to mark changes to any field in the device file status endpoint, not just changes in the status enumerations.

GET /v1/tenants/liberty/devices/8031962043/files

Response 200

{
  "configurationInfo": {
    "activeFileName": "00000BA0",
    "folderName": "00200B23",
    "lastReportedFileName": "00200B23",
    "responseCode": null,
    "status": "upToDate",
    "statusChangedAt": "2019-06-11T20:28:43.708Z",
    "lastModifiedAt": "2019-06-11T20:28:43.708Z"
},
  "firmwareInfo": {
    "activeFileName": "0B72",
    "folderName": "new-firmware",
    "lastReportedFileName": "0A21",
    "responseCode": null,
    "status": "upToDate",
    "statusChangedAt": "2019-06-11T11:32:54.027Z"
    "lastModifiedAt": "2019-06-11T20:28:43.708Z"
}

Did this answer your question?