# Boards

> Create hardware profiles and metadata rules for Infuse-IoT Cloud devices.

Boards describe hardware families, product profiles, or device types. A board groups devices that share hardware assumptions such as SoC, metadata fields, and release compatibility.

Use boards to:

- organise devices by hardware or product family,
- filter devices by board and metadata,
- define which metadata fields operators should capture,
- connect application releases to compatible board targets.

## Boards In The Console

Open **Infuse IoT** > **Boards** to view boards in the linked Infuse IoT organisation.

The board list shows board name, SoC, metadata field count, and update time. Open a board to view its identifiers, owning organisation, and metadata fields.

## Create A Board

From **Infuse IoT** > **Boards**, select **Add board** and provide:

<table>
<thead>
  <tr>
    <th>
      Field
    </th>
    
    <th>
      Use
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      Name
    </td>
    
    <td>
      Human-readable board or product profile name.
    </td>
  </tr>
  
  <tr>
    <td>
      Description
    </td>
    
    <td>
      Operational context for the board.
    </td>
  </tr>
  
  <tr>
    <td>
      SoC
    </td>
    
    <td>
      System on chip used by devices on this board.
    </td>
  </tr>
  
  <tr>
    <td>
      Metadata fields
    </td>
    
    <td>
      Optional field rules used when editing device metadata.
    </td>
  </tr>
</tbody>
</table>

## Metadata Fields

Board metadata fields describe the product-specific device metadata your team expects to maintain.

Each field has:

<table>
<thead>
  <tr>
    <th>
      Property
    </th>
    
    <th>
      Meaning
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      Field name
    </td>
    
    <td>
      Metadata key shown when editing a device.
    </td>
  </tr>
  
  <tr>
    <td>
      Required
    </td>
    
    <td>
      The metadata field must be present when saving device metadata in the console.
    </td>
  </tr>
  
  <tr>
    <td>
      Unique
    </td>
    
    <td>
      The value should identify a device within that board family, such as a serial number or asset tag.
    </td>
  </tr>
</tbody>
</table>

Good metadata fields are stable, operationally useful, and not overloaded. Prefer fields such as `serialNumber`, `assetId`, `customer`, `deploymentSite`, `hardwareVariant`, or `commissioningBatch`.

## API Workflows

Use the API when boards are created from product lifecycle systems or when environments need to be reconciled automatically.

<table>
<thead>
  <tr>
    <th>
      Task
    </th>
    
    <th>
      Endpoint
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      List boards
    </td>
    
    <td>
      <code>
        GET /board
      </code>
    </td>
  </tr>
  
  <tr>
    <td>
      Create a board
    </td>
    
    <td>
      <code>
        POST /board
      </code>
    </td>
  </tr>
  
  <tr>
    <td>
      Read a board
    </td>
    
    <td>
      <code>
        GET /board/id/{id}
      </code>
    </td>
  </tr>
  
  <tr>
    <td>
      List devices for a board
    </td>
    
    <td>
      <code>
        GET /board/id/{id}/devices
      </code>
    </td>
  </tr>
</tbody>
</table>

For request schemas and response shapes, see the [Infuse-IoT Cloud API reference](/api-reference/iot).