NWPLATHW: Hardware Type
An abstract hardware or infrastructure type used by network platforms, such as a server family, switch platform, cloud service, or appliance model.
Default definition. This article describes the default
NWPLATHW definition shipped with DemandFlow. Administrators can add, remove, rename, or re-type fields, change which ones are required, and alter the layout from the Definitions screen in Settings. Your tenant's current schema may differ from what is shown here. To read the current definition at any time, GET the DEFINITION object whose id matches NWPLATHW.Entity properties
| Property | Value |
|---|---|
| Entity code | NWPLATHW |
| Display name | Hardware Type |
| Plural | Hardware Types |
| Level | 6170 |
Use cases
Catalogue entity for abstract hardware/infrastructure types. Not linked to physical inventory (COMPINV) - this is about defining classes of hardware (e. g.
Fields
Hardware Type
| Field | Type | Required | Notes |
|---|---|---|---|
name | text | Yes | Name |
hwCategory | enum | Yes | Category Valid ids: server (Server), storage (Storage), networking (Networking), cloud (Cloud / IaaS), appliance (Appliance), virtualisation (Virtualisation), container (Container Platform), accelerator (Accelerator / GPU). |
vendor | reference → VEN | Vendor | |
description | text (multi-line) | Description |
Relationships
- Lookups:
vendorpoints at aVENrecord. - Related lists:
NWPLATHWVER(formatSUB|NWPLATHW).
Creating a Hardware Type via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "NWPLATHW",
"level": 6170,
"comboKey": "SUB:<your-sub-id>|ENT:",
"name": "Example",
"hwCategory": "server",
"vendor": "",
"description": "Example text."
} Listing Hardware Types records
# All hardware types in your tenant
GET /v1/entities/NWPLATHW/SUB