NewImportProcess prepares an import process but it does not start it. You can use StartProcess method to make it start by specifying idProcess value that is returned by NewImportProcess.

Please note that you cannot activate more than one import process at the same time, however you can prepare many import processes with NewImportProcess and then call StartImportProcesses method that starts all of them in a sequential manner.

Method parameters

NewImportProcess(int idList, int listGUID, idGroup, string xmlDoc, string idGroups, int importType,
int mobileInputType, bool asPending, bool ConfirmEmail, bool asOptOut, bool forceOptIn,
bool replaceGroups, int idConfirmNL)

Creates a new import process for the contacts listed in the xmlFeed.

If the import process is created successfully, then an "idProcess" value identifying it is returned; if not, a ReturnCode is returned.

Please refer to WSMailUpImport.StartImportProcesses for details about allowed data format of each parameter. In particular, please pay attention to the constraints that are described "XML structure" in section for xmlDoc parameter.


Sample ReturnCode


Error codes

Error codeDescription
-400unrecognized error
-401xmlDoc is empty
-402convert xml to csv failed
-403create new import process failed
-410cannot create confirmation email

XML feed

The XML structure for importing subscribers is shown below:

<subscriber email="" Prefix="+001" Number="8889624587" Name="">
<campo1>first name</campo1>
<campo2>last name</campo2>

Phone numbers can be specified in two ways:

<subscriber email="" Prefix="" Number="+0018889624587" Name="">
<subscriber email="" Prefix="+001" Number="8889624587" Name="">

Ruby Example

# Refer to for gem information.
require 'mailup'
m ='username', 'password', 'console_url')
m.new_import_process(:listID => 123456, :listGUID => 123456, :xmlDoc => "XML_STRING", ...)
# => <?xml version=\"1.0\" encoding=\"windows-1252\" ?><mailupMessage><mailupBody><ReturnCode>17</ReturnCode></mailupBody></mailupMessage>