tracklist

Returns the list of user's tracks. Tracks are ordered by opening day time in descending order.

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: “tracklist”.

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

• txtParameter field contains a structure like this:

<?xml version="1.0" encoding="utf-8" ?> 
<tracklist>
	<updateposition>2</updateposition>
	<consumer>27</consumer>
	<maxitem>20</maxitem>
	<time>20101112173025</time> 
</tracklist>

{
  "tracklist": {
    "updateposition": "2",
    "consumer": "27",
    "maxitem": "20",
    "time": "20101112173025"
  }
}

Where

• <updateposition> optional. This field is not useful if getting friend's track list. Can be:

  • 0 (zero) returns tracks with updateposition set to 0 (zero).
  • 1 (one) returns tracks with updateposition set to 1 (one).
  • 2 (two) returns all tracks. This is the default value.

• <consumer> optional. Consumer Id by which search the tracks. If set to 0 (zero) returns tracks of unidentified user.

• <friend> optional. If set return a list of friend's tracks. If also <consumer> field is set, this field will be ignored.

• <from> optional, date and time in UTC. The accepted format is “yyyyMMddhhmmss”. If set returns tracks with the end time greater than or equal to this value.

<to> optional, date and time in UTC. The accepted format is “yyyyMMddhhmmss”. If set returns tracks with the start time less than or equal to this value.

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

• <maxitem> optional. Used for paging results. If set returns tracks 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:

“tracklist20101112173025xxxxxxxxx”

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

Returns a structure like the following:

<?xml version="1.0" encoding="utf-8" ?> 
<furesult>
	<message><![CDATA[ OK ]]></message>
	<items>
		<item>
			<id>10</id>
			<description><![CDATA[Molinella / Ozzano]]></description>
			<autoclosed>null</autoclosed>
			<starttime>20101110110816</starttime>
		</item> 
		<item>
			<id>12</id>
			<description><![CDATA[Molinella / Ferrara]]></description>
			<autoclosed>0</autoclosed>
			<starttime>20101110093010</starttime>
			<endtime>20101110104520</endtime>
		</item>
	</items>
</furesult>

{
  "furesult": {
    "message": " OK ",
    "items": {
      "item": [
        {
          "id": "10",
          "description": "Molinella / Ozzano",
          "autoclosed": "null",
          "starttime": "20101110110816"
        },
        {
          "id": "12",
          "description": "Molinella / Ferrara",
          "autoclosed": "0",
          "starttime": "20101110093010",
          "endtime": "20101110104520"
        }
      ]
    }
  }
}