Create an Inventory Product (BETA)

post

https://resources.uk.eagleeye.com/products/{incomingIdentifier}

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

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Path Params

incomingIdentifier

string

required

The incoming identifier of the unit whose inventory products are being managed.

Body Params

JSON payload for creating or updating an inventory product.

string

required

The unique identifier of the inventory product.

groupId

string

required

The identifier of the group this product belongs to.

name

string

The display name of the product.

description

string | null

An optional description of the product.

imageUrl

string | null

URL of the product image.

supplierId

string | null

The identifier of the product supplier.

supplierName

string | null

The display name of the product supplier.

brand

string | null

The brand of the product.

brandType

string | null

The brand type classification of the product.

lastSoldDate

string | null

The date and time the product was last sold (ISO 8601 / ATOM format).

tags

Headers

Accept-Encoding

string

enum

Defaults to ''

This request HTTP header advertises which content encoding (usually a compression algorithm) the calling application is able to understand. The server selects one of the proposals, use it and informs the client of its choice with the Content-Encoding Response header. Currently supported gzip and deflate. Please note if this request header is not present, no compression will be used.

Allowed:

Connection

string

enum

Defaults to close

This general HTTP header controls (or rather influences) whether the network connection stays open after the current request finishes. If the sent value is keep-alive, the connection should stay in a special state, allowing to be reused for subsequent requests to the same server. Please note these connections will be closed after reaching timeout threshold controlled by EES server (usually after 5 seconds).

Allowed:

X-EES-AUTH-CLIENT-ID

string

required

Client ID, This will be provided by EES and is unique to the company calling the API.

X-EES-AUTH-HASH

string

required

Request Security Hash, calculated using SHA-256 function from concatenated full Request URI Path with Query String(s), Payload and Client Secret.

X-EES-TRANSACTION-ID

string

Unique Reference for the API transaction within the calling company.

Responses

Language

URL

Loading…

Response

Choose an example:

application/json

201EES AIR has successfully processed a Request.

400EES 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)

401EES 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

403EES 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.

404EES AIR Refuse to process that particular Request as requested/referenced resource could not be found.

409EES 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.

415EES AIR is not able to understand that request due to not supported Content-Type value.

429EES AIR refuses to process that particular Request as Client's API Requests Limit was exceeded.

500EES AIR refuses to process that particular Request due to Unexpected Server Error.

503EES AIR refuses to process that particular Request due to Service(s) being Unavailable (i.e. Scheduled Maintenance)

504EES AIR refuses to process that particular Request due to Networking Issues