addUser

Request parameters

Parameter	Data type	Description
callback	string	Specifies the action for this request, which in this case is "addUser".
username	string	End user's username. Example: bob
password	string	End user's password. Example: abc123
email	string	End user's email. Example: [email protected]
subscription_id	numeric	Vendo's subscription identifier. Example: 123456789
site_id	numeric	Vendo's site identifier. Example: 123456789
customer_id	numeric	Vendo's customer identifier. Example: 123456789
firstname	string	End user's first name. Example: Robert
lastname	string	End user's last name. Example: Johnson
street	string	End user's street address. Example: Sant Pere Mes Alt 20, 1
zip	string	End user's zip code. Example: 90350
city	string	End user's city. Example: Barcelona
country	string	End user's country. 2-letter ISO 3166-1 alpha-2 format. Example: US
language	string	End user's language. 2-letter ISO 639-1 format. Example: en
ip	string	End user's IP. May be IPv4 or IPv6 formatted. Example: 8.8.8.8
merchant_reference	string	Your custom passed reference in the join link via the ref parameter. Example: 123
is_test	boolean	Whether or not this request is related to a test transaction or subscription. 0 for no (real transaction) 1 for yes (test transaction)

Your server must reply with one of these response formats:

OK (Response code 1)

Reply with this if the request was successful, the end user was granted access.

Example:

<?xml version="1.0" encoding="UTF-8"?>
<postbackResponse>  
 <addUser>       
  <code>1</code> 
 </addUser>
</postbackResponse>

ERROR (Response code 2)

Reply with this if you encountered an unexpected problem with the request.

Include a custom error message with your message for tracing/debugging. Make sure this error message is meaningful because it is stored to a logfile for later debugging.

Example:

<?xml version="1.0" encoding="UTF-8"?>
<postbackResponse> 
 <addUser>  
  <code>2</code>  
  <errorMessage>Custom error message</errorMessage> 
 </addUser>
</postbackResponse>