3.0 Get an Asset

3.2 Data Returned

Back to Index
Returned information:

An asset message

<!ELEMENT assetlist (asset*)>
<!ATTLIST assetlist ver CDATA #REQUIRED>
<!ELEMENT asset (name, tag, vin, fleet, type, subtype, exsid, mileage, location,
mileoffset, radioaddress, mfg, inservice, inspdate, yardstat, opstatus)>
<!ATTLIST asset id CDATA #REQUIRED>
<!ELEMENT name (#PCDATA)>
<!ELEMENT tag (#PCDATA)>
<!ELEMENT vin (#PCDATA)>
<!ELEMENT fleet (#PCDATA)>
<!ELEMENT type (#PCDATA)>
<!ATTLIST type id CDATA #REQUIRED>
<!ELEMENT subtype (#PCDATA)>
<!ATTLIST subtype id CDATA #REQUIRED>
<!ELEMENT exsid (#PCDATA)>
<!ELEMENT mileage (#PCDATA)>
<!ELEMENT location (#PCDATA)>
<!ELEMENT mileoffset (#PCDATA)>
<!ELEMENT enginehouroffset (#PCDATA)>
<!ELEMENT radioaddress (#PCDATA)>
<!ELEMENT mfg (#PCDATA)>
<!ELEMENT inservice (#PCDATA)>
<!ELEMENT inspdate (#PCDATA)>
<!ATTLIST inspdate id CDATA #IMPLIED>
<!ATTLIST inspdate type CDATA #IMPLIED>
<!ELEMENT yardstat (yard, stat)>
<!ELEMENT yard (#PCDATA)>
<!ELEMENT stat (#PCDATA)>
<!ATTLIST stat timestamp CDATA #REQUIRED>
<!ELEMENT opstatus (#PCDATA)>
<!ATTLIST opstatus timestamp CDATA #IMPLIED>

Note: The <inspdate> element contains the Unix epoch timestamp of the latest inspection for this asset. The id element is the inspection id. If the asset has no inspections, then the element is empty, like this: <inspdate/> This element was added in API protocol version 1.03.
The <inservice> date element and <mfg> element were added in API protocol version 1.03.
The <yardstat> element and inspection config information were added in API protocol version 1.05.
The opstatus element was added was added in protocol version 1.06. See the request data for an explanation of the different values.
The id attribute was added in protocol version 1.06. This is the internal system id of the asset object.

Example Request:

http://development.zonarsystems.net/interface.php?action=extgetasset&reqtype=tag&target=5467