The addUser postback gets posted when an end user has successfully completed a signup transaction. It's posted so your system knows that the user should be granted access to your site.

Request parameters

ParameterData typeDescription
callbackstringSpecifies the action for this request, which in this case is "addUser".
usernamestringEnd user's username.
Example: bob
passwordstringEnd user's password.
Example: abc123
emailstringEnd user's email.
Example: [email protected]
subscription_idnumericVendo's subscription identifier.
Example: 123456789
site_idnumericVendo's site identifier.
Example: 123456789
customer_idnumericVendo's customer identifier.
Example: 123456789
firstnamestringEnd user's first name.
Example: Robert
lastnamestringEnd user's last name.
Example: Johnson
streetstringEnd user's street address.
Example: Sant Pere Mes Alt 20, 1
zipstringEnd user's zip code.
Example: 90350
citystringEnd user's city.
Example: Barcelona
countrystringEnd user's country. 2-letter ISO 3166-1 alpha-2 format.
Example: US
languagestringEnd user's language. 2-letter ISO 639-1 format.
Example: en
ipstringEnd user's IP.
May be IPv4 or IPv6 formatted.
merchant_referencestringYour custom passed reference in the join link via the ref parameter.
Example: 123
is_testbooleanWhether 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.


<?xml version="1.0" encoding="UTF-8"?>

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.


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