Provisioned Devices

User should be able to provision devices from inventory into any sub account of their choice.

Once the device has been moved to any account, it should be capable of applicable functional activities.

The API will do authorization for accountId, solomonId and validate the payload. If validation is success, then do separate the identifiers into chunks of 50 and it will create batch task its return task id.

Once a task has been created successfully,. To see the status of the task, click here /task/{taskId}

Task status should be Pending, Completed, Partial Success, or Failed.

API will support below options in the request payload

  • Entity Identifier List (serialNumber)
  • memberSearch

Required Permission: manufacturing-update and device-read

Sample input request body:

Sample payload for Entity Identifier List.

{ 
"entityType": "provisionedDevice", 
"solomonId": "QATEST1", 
"accountId": 2, 
"entityIdentifierList": [ 434084434084, 379517379517 ], 
"entityIdentifierType": 
"serialNumber", 
"taskNickName": "assignRegion for 2 devices", 
"bulkOperation": { "actionType": "assignRegion", 
"actionDetails": { "provisionAccountId": 11024 } }, 
"hierLevel": "ALL" 
}

Sample payload for Search payload.

{ 
 "accountId": 2, 
 "entityType": "provisionedDevice", 
 "taskNickName": "Activate: 1 Inventory Devices; 20240509", 
 "bulkOperation": { 
 "actionType": "assignRegion", 
 "actionDetails": { 
 "provisionAccountId": 11024 } }, 
 "search": { 
 "searchTerms": { 
 "status": "Enabled", 
 "solomonId": "QATEST1", 
 "serialNumber": "*2024022115*" } }, 
 "hierLevel": "ALL", 
 "solomonId": "QATEST1", 
 "currRegion": "Inventory" 
 }
Language
Authorization
Click Try It! to start a request and see the response here!