Provision several Devices in bulk. Devices to be provisioned are detailed in a CSV file sent with the request.
CSV File Contents
The CSV file contains the following column headers:
| Name | Required? | Type | Value |
|---|---|---|---|
| IMEI | true | string | IMEI of the Device |
| FSN | true | string | Serial Number of the Device |
| NAME | true | string | Device name |
| DISPLAY_NAME | false | string | The Display name of the Device |
| BLUEPRINT_ID | false | string | ID of the Blueprint to apply to this Device |
| BLUEPRINT_VERSION | false | int | Version of the Blueprint to apply to this Device |
| DEPLOY_FIRMWARE | false | bool | Should the firmware attached to the supplied Blueprint be installed? Default = false |
| TAG.(key) | false | string | Replace (key) with the Tag key you wish to apply to the Device. Multiple Tag columns can be specified |
| METADATA.(key) | false | json | Replace (key) with the Metadata key you wish to apply to the Device. Multiple Metadata columns can be specified |
Required columns must be included in the CSV file, and values must be included for each row. For optional columns, values can be left blank, or alternatively the column may be ommitted entirely.
Column headers are case-sensitive.
Tag and Metadata columns are special - the user may supply any number of them so long as they are unique. Examples include:
| Example Column | Example Value |
|---|---|
| TAG.foo | bar |
| TAG.location | NYC |
| METADATA.color | orange |
| METADATA.size | "medium" |
| METADATA.foo.bar | ["a",true,1.2] |
Octave will attempt to parse metadata values as JSON. Failing that, they will be read as a string.
Some columns are conditional on others. For example, BLUEPRINT_VERSION and DEPLOY_FIRMWARE cannot be included without BLUEPRINT_ID.
IMEI, FSN, and NAME values must be unique.