Bulk Create/Edit/Delete devices via CSV file.

CSV Format

The CSV file must have either 21 columns (device-only, legacy) or 25 columns (device + SIM, EIQ-5996), in the following order:

Operation Types

• Create: When both Delete and Update columns are false or empty
• Update: When Update column is true
• Delete: When Delete column is true

Note: Delete and Update cannot both be true for the same row.

Validation Rules

• Heartbeat Period: Must be an integer >= 0. Negative values are not allowed. Value of 0 is treated as "not set".
• Boolean fields (Active, Enforce Secure MQTT, Delete, Update): Must be true, false, or empty.
• Metadata: Must be in format key:value pairs separated by semicolons.
• Tags: Semicolon-separated list of tag names.
• ICCID (SIM): When provided, must be 18-22 digits and unique platform-wide.

SIM behavior (25-column variant only)

• Create row + ICCID populated: device is created and a SIM is created and linked to it.
• Create row + SIM fields populated but ICCID empty: device is created, no SIM is created (a warning is raised by /devices/csv_validate).
• Update row + ICCID populated, no SIM exists: device is updated and a new SIM is created.
• Update row + ICCID populated, SIM already exists: device is updated and the existing SIM is updated in place (its id is preserved).
• Update row + ICCID empty: device is updated; the existing SIM (if any) is left untouched.
• Delete row: device is deleted; any associated SIM is removed automatically by FK cascade.

Atomicity

Device + SIM creation is atomic per row. If the SIM cannot be created or updated (validation error, ICCID conflict, DB error), the device write is rolled back so we never leave an orphan device. The row is reported as failed in the bulk response.

Bulk response summary

The bulk_response.metadata JSONB field is populated with SIM-specific counters when SIM-related work happened during the import:

{
  "metadata": {
    "sims_created": 10,
    "sims_updated": 3,
    "sims_deleted": 1,
    "sims_failed":  0
  }
}

Update Behavior

When updating devices, the following fields are replaced (not merged):

• Tags: The entire tags list is replaced with the values from the CSV. To add a new tag while keeping existing ones, include all existing tags plus the new one in the CSV.
• Metadata: The entire metadata object is replaced with the values from the CSV. To add a new key while keeping existing ones, include all existing key:value pairs plus the new one in the CSV.

If these columns are left empty during an update, the existing values are preserved.

Limits

• Maximum 1000 devices per upload