POST public-api/transactions/public/asset/check-out

Required, the asset tag of the asset being checked in

The current site of the asset being checked in, required for multi-quantity assets

The current location of the asset being checked in, required for multi-quantity assets

The current asset tag of the group the checked in asset belongs to, required for multi-quantity assets

The new site of the checked in asset, optional

The new location of the checked in asset, optional

The new asset tag of the group the checked in asset belongs to, optional

Optional, the date the asset is due back

Optional, the date the asset was checked out, will default to Now

The vendor number of the assignee that is checking in the asset, required for multi-quantity assets

The customer number of the assignee that is checking in the asset, required for multi-quantity assets

The employee number of the assignee that is checking in the asset, required for multi-quantity assets

Required for multi-quantity assets, the amount of the asset being checked out

Optional, identifier for device checking out the asset (i.e. a PC Name, Kiosk name, mobile device)

Optional, note associated with the check out transaction

during check out, the asset condition could be set. if a valid value is specified, then the new asset condition value will be used to update the asset record as well as stored into the check out transaction history.

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.