trackpointsloadbydate
trackpointsloadpubbydate
Returns user's points or public points or friend's points between given dates. If it is used “trackloadpubbydate” command, public tracks can be read without giving username and password.
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: “trackpointsloadbydate” or “trackpointsloadpubbydate”.
-
txtFormat optional field specifies txtParameters and response formats. more info.
-
txtParameter field contains a structure like this:
Note: both commands' root tag is <trackpointsloadbydate>
Where
-
<from> optional. The start of interval of points to search. If no value is set the backend server will return all points from the beginning.
-
<to> optional. The end of interval of points to search. If no value is set the backend server will return all points till the end.
-
<consumer> mandatory. Consumer Id by which search the tracks.
-
<interestpoints> optional. Can be:
-
0 (zero) MyWakes does not send POIs. This is default value.
-
1 (one) MyWakes sends POI.
-
<lasttime> optional. In format yyyyMMddhhmmss. If set the backend server will return only points with a date greater then this user value.
-
<minitem> optional. Used for paging results. If set returns points greater than this value.
-
<maxitem> optional. Used for paging results. If set returns points 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 2000.
-
<simplifiedmax> optional. Only if a track is closed, and no values are set for <MaxItem> and <MinItem>, permits to have track points in simplified mode.
-
<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” + “from” + + “to” + “time” + “generated character to 32”.
Looking at the previous example, the string on which calculate the check will be:
“trackpointsloadbydate20131031080”
Therefore the txtProvider field will be:
“76a865d4-fab8-51cd-ba78-2da325f6955a”