POST public-api/transactions/item/add

Required: the unique identifier for this item

Required: the cost of an individual unit cost of the inventory being added

the date the inventory was acquired

the customer associated with the transaction

Required: the site the inventory is being placed at. If ParentContainerId is specified, then this field should be null or empty.

Required: the location the inventory is being placed at within the site If ParentContainerId is specified, then this field should be null or empty.

Instead of adding inventory quantity using LocationCode and SiteName, the Inventory Quantity can be added (or nested) in a container (such as a carton, box, tote, tub, pallet, cage, etc). The License Plate Number must already exist in the system prior to use.

the vendor associated with the transaction

Required: the amount of inventory to add

the date code of the inventory

This value should be specified ONLY if a new container is being added to the system. When a new container is added, the Quantity specified must be exactly 1. If NewContainerId already exists, then an error will be returned. If a new License Plate Number is being added and nested to an existing parent container instead of a site/location, then the value ParentContainerId must be specified, and ParentContainerId must already exist. THIS VALUE MUST BE GLOBALLY UNIQUE

the lot of the inventory

the unique serial number of the inventory. This value must be unique for the specified ItemNumber. When SerialNumber is specified, the Quantity must be exactly 1.

The reference number associated with the transaction. This value is used to tag a transaction with a searchable/filterable value.

Sometimes during add or receive (when inventory quantity is being added), we will need to specify an (optional) Purchase Order Number. If the purchase Order Number does NOT exist, then the error 'Order Not Found' will be returned.

The name or ip address of the mobile device or computer/workstation that is making the Inventory Add request

Type specific result that always depends on the function called.

List of Messages. All APIs should return messages. If an API function returns an error you can find more information about the error or errors in this collection of messages.

This is a global batch number generated by a mass group of transaction records to be returned to the consumer on each call to rolling transaction rules. This requests that each group of Move/Add/Remove transaction batches is tied together. In prior products (such as Mobile Asset Cloud), all are set to null and the only time when the batch number is generated is for multiple check-out transactions but the old is to generate for each responsible party.

True if an API function result has an error message in the results. If this is false, the function succeeded but other informative messages may be available.

True if an API function call could not be fully posted to the server or the results could not be fully returned.

True if any message is available.

True if the server sent part of the data and there is more data available. Use with paging APIs to fetch data one page at a time.

This is the total number of records available in the database based on the query and filer conditions provided. It is possible that the value can change from call to call as users add and delete records so this should not be used to page through multiple recordsets of data. This is used, for example, to set relative scroll bar sizes. When paging through data using functions like the assetadvancedinfosearch, calculating TotalRecordsLongCount for every page full of data is an time-consuming operation. To avoid that extra calculation, and help prevent throttling, assign TotalRecordsLongCount to TotalCountFromPriorFetch in the AdvancedSearchParameters to skip recalculating this total page count and to page thru the records faster.