Modify an existing asset object. New values for any asset attributes may be assigned to the asset.
|The asset to modify. If specified a reqtype (request type) must be specified as well.
|Flag to identify the key being used to identify the asset. Acceptable values:
|When using reqtype of tag or fleet this must also be specified in version 2. See asset types for more details.
|Cust assigned ident Any text, 20 char max. Must be unique.
|Asset type label. The type the asset will have when the edit is completed. Assets must have a type assigned to them.
|Location name this asset is assigned to. Must be a valid location name.
|If any optional information is omitted, the asset will be assigned an empty or default value.
|License tag number. Any text, 20 character max.
|VIN number Any text, 40 char max Must be unique.
|Unique identifier used by the external maint system. Any text, 40 Char max. Must be unique.
|The asset inservice date. Unix epoch timestamp. (UTC)
|Zonar RFID tag number. Integer, the tagid type combination must be unique if supplied.
|Offset to be applied to mileage readings obtained from RFID equipped hubometers in inspections for this asset.
|The asset engine_hour_offest is derived by taking the difference between the asset's chronometer and the GPS unit's chronometer. Most often, the GPS unit's chronometer will be 0, but this needs to be verified. The gps zones reported in the engine hour are restricted to the last know location of the asset before or at power-off.
|This gives the option to set an asset to active 1 or inactive 2. If no type is set then the default is active.
|Address used by wireless data link for hand held download stations.
|Label of the subtype for the new asset.
|home LOI1 for this asset.
start date parameter.
|The date odometer_offset is applied to.
1 LOI means Location of Interest; called "Zone" in the GPS tools and reports found within the Ground Traffic Control web application.
A success or error message.
Example Success Reply
Example Error Reply