trackconsumerslist

Returns the list of the consumers that own tracks. If unassigned tracks are present this command returns also a consumer with ID equal to 0 (zero).

Command's fields description:

  • txtUser1 field is the “username” of MyWakes account.

  • txtUser2 field is the “password” of MyWakes account.

  • txtCommand field contains the command: “trackconsumerslist”.

  • txtFormat optional field specifies txtParameters and response formats. more info.

  • txtParameter field contains a structure like this:

<?xml version="1.0" encoding="utf-8" ?> 
<trackconsumerslist>
	<time>20101112173025</time> 
</trackconsumerslist>
{
  "trackconsumerslist": {
    "time": "20101112173025"
  }
}

 

Where

  • <completelist> optional. Set if the list must be complete or those who own at least one track and can be:

    • 0 (zero) returns only consumers who own at least one track. This is the default value.

    • 1 (one) returns all consumers.

    • 2 returns only the consumers who can turn on or turn off antitheft.

  • <devicetype> optional. Sets if the command must return only consumers that are using the requested device type.

  • <minitem> optional. Used for paging results. If set returns consumers greater than this value.

  • <maxitem> optional. Used for paging results. If set returns consumers less than this value. Note that order to prevent your system from being flooded with oversized responses, the number of messages that will be returned on a single response is limited to 500.

  • <time> mandatory, date and time in UTC. The accepted format is “yyyyMMddhhmmss”.

  • txtProvider field must contain the application calling ID and generated characters.

  • txtSignature field must contain the signature based on the string made of “Command Name” + “time” + “generated character to 32”.

Looking at the previous example, the string on which calculate the check will be:
“trackconsumerslist20101112173025”


Therefore the txtProvider field will be:
“76a865d4-fab8-51cd-ba78-2da325f6955a”

Returns a structure like the following:

<?xml version="1.0" encoding="utf-8" ?> 
<furesult>
	<message><![CDATA[ OK ]]></message>
	<items>
		<item>
			<id>27</id>
			<callsign><![CDATA[BO123456]]></callsign>
			<description><![CDATA[FIAT]]></description>
			<tottrack>8</tottrack>
			<lasttracktime>20101004163025</lasttracktime>
			<odometer>25</odometer>
			<hoursmeter>40.5</hoursmeter>
		</item> 
		<item>
			<id>12</id>
			<callsign><![CDATA[AZ1234XZ]]></callsign>
			<description><![CDATA[FURGONE]]></description>
			<tottrack>22</tottrack>
			<lasttracktime>20101007184227</lasttracktime>
			<odometer>120000.5</odometer>
			<hoursmeter>334.5</hoursmeter>
		</item>
	</items>
</furesult>
{
  "furesult": {
    "message": " OK ",
    "items": {
      "item": [
        {
          "id": "27",
          "callsign": "BO123456",
          "description": "FIAT",
          "tottrack": "8",
          "lasttracktime": "20101004163025",
          "odometer": "25",
          "hoursmeter": "40.5"
        },
        {
          "id": "12",
          "callsign": "AZ1234XZ",
          "description": "FURGONE",
          "tottrack": "22",
          "lasttracktime": "20101007184227",
          "odometer": "120000.5",
          "hoursmeter": "334.5"
        }
      ]
    }
  }
}

 

Where

  • <message> contains OK or Error description
  • <items> if the command has succeeded and <message> is OK this tag exists and contains the list of the track with following node:
    • <item> each element of the list, can be repeated more times and contains the following tags:
      • <id> consumer's Id: it's the only way to identify the consumer and get the consumer's related tracks
      • <callsign> the consumer's identifier
      • <description> the consumer's description set by the user
      • <tottrack> the total number of the existing tracks for that consumer
      • <lasttracktime> the UTC starting date and time of the last track in yyyyMMddhhmmss format
      • <odometer> the odometer's value for the current consumer
      • <hoursmeter> the hoursmeter's value for the current consumer
      • <lat> the point's latitude in degree and decimal degrees. If the position is in the southern hemisphere the value will be negative so it will be preceded by a minus sign. This is the last known latitude. This field is present only if input parameter value <completelist> is equal to 2 (two)
      • <lon> the point's longitude in degree and decimal degrees. If the position is in the western hemisphere the value will be negative so it will be preceded by a minus sign. This is the last known longitude. This field is present only if input parameter value <completelist> is equal to 2 (two)
      • <latlontime> UTC date and time of the last known position. This field is present only if input parameter value <completelist> is equal to 2 (two)
      • <antitheft> represents the status of anti theft, this is the last known longitude. This field is present only if input parameter value <completelist> is equal to 2 (two):
        • 0=anti theft not activated
        • 1=anti theft activated

If MyWakes server returns an error, the format of this answer is described in the error section.

Terms Of Use | Privacy Statement | Company info
  • © Cedac Sistemi srl
  • Head office: Via Toscana, 3 40035 Castiglione dei Pepoli (Italy) Tel.: +39 0534-93811 Fax: +39 0534-93899
  • Branch office: Via del Lavoro, 47 40033 Casalecchio di Reno (Italy)
  • Branch office: Via Parini, 1 40033 Casalecchio di Reno (Italy)
  • Share capital Euro 26,000.00 - Company Register of Bologna / VAT no / fiscal code 01695261204