AI-generated Key Takeaways
- 
          
Creates a signed device under a node or customer using a POST request.
 - 
          
Requires a JSON Web Token signed with a CPI private key and a unique installer ID in the request body.
 - 
          
Returns the created device details upon successful completion.
 - 
          
Needs authorization with the
https://www.googleapis.com/auth/userinfo.emailscope. 
HTTP request
POST https://sasportal.googleapis.com/v1alpha1/{parent=customers/*}/devices:createSigned
The URL uses gRPC Transcoding syntax.
Path parameters
| Parameters | |
|---|---|
parent | 
                
                   
 Required. The name of the parent resource.  | 
              
Request body
The request body contains data with the following structure:
| JSON representation | |
|---|---|
{ "encodedDevice": string, "installerId": string }  | 
                |
| Fields | |
|---|---|
encodedDevice | 
                  
                     
 
 Required. JSON Web Token signed using a CPI private key. Payload must be the JSON encoding of the [Device]. A base64-encoded string.  | 
                
installerId | 
                  
                     
 Required. Unique installer id (cpiId) 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