usercreate

Creates a new user.

Command's fields description:

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

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

• txtCommand field contains the command: “usercreate”.

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

• txtParameter field contains a structure like this:

<?xml version="1.0" encoding="utf-8" ?> 
<usercreate>
	<email>pippo@pippo.com</email>
	<securityquestion>Nome della mamma</securityquestion>
	<securityanswer>Maria</securityanswer>
	<imei>123456789012345</imei>
	<consumer>I1234</consumer>
	<time>20101112173025</time> 
</usercreate>

{
  "usercreate": {
    "email": "pippo@pippo.com",
    "securityquestion": "Nome della mamma",
    "securityanswer": "Maria",
    "imei": "123456789012345",
    "consumer": "I1234",
    "time": "20101112173025"
  }
}

Where

• <email> mandatory. The e-mail address of the new user.

• <emailconfirmed> optional. If mail address is certain and it is not necessary to send confirmation mail, it is possible to set this value to 1 (one). Default value is 0 (zero).

• <securityquestion> optional. Question that will be asked in case of password reset.

• <securityanswer> optional. Answer that will be asked in case of password reset. If question or answer are not specified MyWakes server will set a default security question: “What procedure has been created the user?” and as default security answer the calling application name. The user will then confirm his new account.

• <imei> mandatory. Device's IMEI code.

• <consumer> optional. If set the server will create a new consumer with this call sign linking it with the just created user.

• <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” + “mail” + “time” + “generated character to 32”.

Looking at the previous example, the string on which calculate the check will be:
“usercreatepippo@pippo.com2010111”

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>
	<creationresult>0</creationresult>
	<creationmessage>The user account was successfully created!</creationmessage>
</furesult>

{
  "furesult": {
    "message": " OK ",
    "creationresult": "0",
    "creationmessage": "The user account was successfully created!"
  }
}