---
title: "Create an Inventory Group (BETA)"
method: POST
path: "/products/{incomingIdentifier}/groups"
tags: ["Product Inventory"]
---

# Create an Inventory Group (BETA)

`POST /products/{incomingIdentifier}/groups`

## Request

- Base URL: `https://resources.uk.eagleeye.com`
- URL: `https://resources.uk.eagleeye.com/products/{incomingIdentifier}/groups`
- Auth: none declared. Required headers: `X-EES-AUTH-CLIENT-ID`, `X-EES-AUTH-HASH`

This API endpoint allows the calling unit to create a new inventory group for their child unit as specified by its `incomingIdentifier`.

## Path parameters

- `incomingIdentifier` string, string, required

## Headers

- `Accept-Encoding` '''' | ''gzip'' | ''deflate'' | ''gzip,deflate'' | ''deflate,gzip'', string
- `Connection` 'keep-alive' | 'close', string
- `Content-Type` string, string
- `X-EES-AUTH-CLIENT-ID` string, string, required
- `X-EES-AUTH-HASH` string, string, required
- `X-EES-TRANSACTION-ID` string, string

## Request body

- InventoryGroupPostRequestEntity
  - `id` string, required: The unique identifier of the inventory group.
  - `name` string, required: The display name of the inventory group.
  - `type` string, required: Group type.
  - `description` string: Optional description of the inventory group.
  - `parentId` string, nullable: Optional parent group identifier.

## Response `201`

EES AIR has successfully processed a Request.

- InventoryGroupEntity
  - `id` string: The unique identifier of the inventory group.
  - `name` string, nullable: The display name of the inventory group.
  - `type` string: The inventory group type.
  - `description` string: An optional description of the inventory group.
  - `parentId` string, nullable: The unique identifier of this group's parent. Null for root groups.
  - `level` integer: The depth level of the group in the hierarchy (root is 1).
  - `hasChildren` boolean: Whether the group has one or more child groups.
  - `parent` InventoryGroupEntity (recursive)

## Other responses

- `400`: EES AIR Refuse to process that particular Request as there is something wrong with the Request (e.g., missing Mandatory Request parameter or Mandatory Request Payload attribute is missing, Request payload cannot be processed, etc)
- `401`: EES AIR Refuse to process that particular Request due to Authentication error. This could be caused by missing mandatory AUTH header(s), invalid Hash calculation, invalid or inactive API Key used, etc
- `403`: EES AIR Refuse to process that particular Request due to Request Authorization error(s). This indicates that used API Key has not got required permissions to perform this operation.
- `404`: EES AIR Refuse to process that particular Request as requested/referenced resource could not be found.
- `409`: EES AIR understands this request, but refuse to process it, due to present Conflict with the current state of the target resource or because performing this operation would lead to a Conflict within AIR.
- `415`: EES AIR is not able to understand that request due to not supported `Content-Type` value.
- `429`: EES AIR refuses to process that particular Request as Client's API Requests Limit was exceeded.
- `500`: EES AIR refuses to process that particular Request due to Unexpected Server Error.
- `503`: EES AIR refuses to process that particular Request due to Service(s) being Unavailable (i.e. Scheduled Maintenance)
- `504`: EES AIR refuses to process that particular Request due to Networking Issues

---

[API](https://skmtc.dev/eagleeye/apis/resource-api.md) - [All operations](https://skmtc.dev/eagleeye/apis/resource-api/llms.txt) - [OpenAPI document](https://skmtc.dev/eagleeye/apis/resource-api/revisions/10217d37fdc5?raw)