AI-generated Key Takeaways
-
This documentation outlines the process for updating a signed device using a
PATCH
request to the specified endpoint. -
The request requires path and body parameters, including device name, encoded device data, and installer ID.
-
If successful, the response returns the updated device information.
-
Authorization requires the
https://www.googleapis.com/auth/userinfo.email
scope.
Updates a signed device
.
HTTP request
PATCH https://sasportal.googleapis.com/v1alpha1/{name=customers/*/devices/*}:updateSigned
The URL uses gRPC Transcoding syntax.
Path parameters
Parameters | |
---|---|
name |
Required. The name of the device to update. |
Request body
The request body contains data with the following structure:
JSON representation | |
---|---|
{ "encodedDevice": string, "installerId": string } |
Fields | |
---|---|
encodedDevice |
Required. The JSON Web Token signed using a CPI private key. Payload must be the JSON encoding of the A base64-encoded string. |
installerId |
Required. Unique installer ID (CPI ID) from the Certified Professional Installers database. |
Response body
If successful, the response body contains an instance of Device
.
Authorization Scopes
Requires the following OAuth scope:
https://www.googleapis.com/auth/userinfo.email