Page Comparison

CreateList_st method allows to create a new list in MailUp, using default values for lists. For new integrations with MailUp it has to be preferred to similar method MailUpSend If you need to configure more parameters, please refer to WS_MailUpManage.CreateList.

Method parameters

This method is used when an external application managing several companies/brands uses one single MailUp console. An example of this is the integration between MailUp and Microsoft Dynamics CRM: one CRM system and one MailUp console allow to manage different companies. Adding a new company is an operation entirely managed in the CRM system, which then creates within MailUp a new list, independent from the others. We recommend to limit the number of lists, in order to preserve the optimal performance of the MailUp console.

...

• string CreateList_st(string accessKey, string name, stringautoId)
  • accessKey: access key obtained using the LoginFromId method
  • name: list identifier
  • autoId: identifier which allows MailUp to know if a list was created in an automated context or not. In the Microsoft Dynamics CRM it corresponds to the ORGUNIQUENAME. If this value is null, or an empty string, the list will not be associated to an automatic creation

SOAP Examples

<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:ws="http://services.mailupnet.it/WS">
   <soap:Header/>
   <soap:Body>
      <ws:CreateList_st>
         <!--Use accessKey value that is returned by LoginFromId method-->
         <ws:accessKey>HzAgwRRJaAKBtkgNWpkAuURfV4SxMm6T3HJegRuSkUivKJElNNcmSQe8nqGyoM9</ws:accessKey>
         <ws:name>My new list</ws:name>
         <ws:autoId>MYUNIQUEID</ws:autoId>
      </ws:CreateList_st>
   </soap:Body>
</soap:Envelope>

...

The XML string will have the following features:

• One root node <CreateLists_st>.
• One <errorCode> node, that contains the error ID (zero when successful)  
• One <errorDescription> node, that contains the error details (empty when successful)  
• One node <Lists>, contained in the root node.
• One node <List> with the attributes Guid, Id and Name. These contain respectively the GUID of the list, the ID of the list and the name of the list provided at entrance.

...