On this page:
It is recommended that you do not create a new list for each campaign, to avoid performance issues we suggest you to not exceed the limit of 100 lists for each console account.
Lists
Note: methods for deleting MailUp lists through REST API are not yet available
Get List country codes
Description | Return the list of available country codes to create or update a list |
---|---|
HTTP Method | GET |
URL | http://services.mailup.com/API/v1.1/Rest/ConsoleService.svc/Console/List/Countries |
Reference | Go to automated doc |
JSON request (example) | none |
JSON response (example) | |
Paging and filtering (example) |
Create List
Now the procedure to create a new list is easier and coherent with the information you provide creating it using your MailUp platform.
We suggest to use the following new method to create a new list, but if you prefer you can continue using the old method that you find in the expand box below.
Happy list creation!
What are mandatory fields?
Mandatory fields are the required information you need to provide to create a new list. These information are the same you need to provide when you create a new list using your MailUp platform.
Here's the list of mandatory fields:
Field name | Type | Description |
---|---|---|
Name | String | List name (max 50 characters) |
Business | Boolean | True if your mailing is directed to businesses |
Customer | Boolean | True if your mailing is directed to consumers |
OwnerEmail | String | "FROM" email: the email address that is sending the message. Make sure that it is a recognizable address (e.g. it uses your Web site domain). |
ReplyTo | String | If your newsletter asks for a reply from the recipients, you may want the replies to be sent to a different address from the "FROM" email. Enter the reply-to address here: it must be a valid email address. If you leave the field blank, the "FROM" address (see "owneremail" field) will be used. |
DisplayAs | String | This is the name that will be displayed in the "To" section of the e-mail message heading. Name can be customized with dynamic fields using "campoN" labels (e.g. campo1,campo2, etc.), where N is the progressive number of the dynamic field |
NLSenderName | String | Email sender name: the person or entity that is sending the message. It could simply be your company name. |
CompanyName | String | The name of the company that is responsible for the messages sent out form this list. This field and the others that follows should be included as "sender information" in each message sent. Please refer to this page for more details |
ContactName | String | The contact reference name |
Address | String | The company's address |
City | String | The company's city |
CountryCode | String | The company's country. Please use one of the Country codes provided by the method Get List of Country codes. |
PermissionReminder | String | Use this field to remind recipients of why they are receiving messages. For example, you can use a message like this:You are receiving this message because you registered on our Web site and agreed to receive email communication from us. |
WebSiteUrl | String | The company's web site url |
Now that you know what we need to create your new list, let's create it!
Get started
Description | Create a new list |
---|---|
HTTP Method | POST |
URL | https://services.mailup.com/API/v1.1/Rest/ConsoleService.svc/Console/List |
Reference | |
JSON request (example) |
|
JSON response (example) | { "IdList": 19, "ListGuid": "57f9c675-63d6-498f-91b6-7f60f9f30b2e", "Name": "New Arrivals", "Description": "", "NLSenderName": "Your list name", "OwnerEmail": "jane@example.com", "PermissionReminder": "Your permission reminder", "Address": "Your address", "Business": true, "City": "Your city", "CompanyName": "Your company", "ContactName": "Your name", "CountryCode": "IT", "Customer": true, "DisplayAs": "Your sender name", "Phone": "", "PostalCode": "", "ReplyTo": "mike@example.com", "StateOrProvince": "", "WebSiteUrl": "www.mailup.it" "BouncedEmail": null, "Charset": "UTF-8", "ConversionlabTrackCode": "", "DefaultPrefix": "0039", "Disclaimer": "Per l'informativa sulla privacy D.Lgs 196/2003 visitare l'home page del sito. <br/> Policy AntiSPAM garantita da <a href=\"http://www.mailup.it/email-marketing/policy-antispam.asp\" target=_blank><img src=\"http://doc.mailupnet.it/logo_small_R.gif\" border=\"0\" align=\"middle\" /></a>", "Format": "html", "FrontendForm": true, "HeaderListUnsubscriber": "<[listunsubscribe]>,<[mailto_uns]>", "HeaderXAbuse": "Please report abuse here: http://www.mailup.it/email-marketing/Policy-antispam_ENG.asp", "KBMax": 100, "LinkTrackingParameters": "", "MultiOptoutList": "19", "MultipartText": true, "NotifyEmail": "", "OptoutType": 3, "Public": true, "ScopeCode": 0, "SendConfirmSms": false, "SendEmailOptout": false, "SmsSenderName": "", "SubscribedEmail": true, "TimeZoneCode": "UTC+01:00.0", "TrackOnOpened": true } |
Paging and filtering (example) |
Advanced
As you have seen in the response of the previous section, a list has many parameters that during creation you can inherit from a specified list or a default table. But sometimes you could have to create a list configuring not mandatory (like a description) or technical (like the maximum newsletter size) parameters. To get more in-depth, the following table shows the optional fields.
Field name | Type | Description |
---|---|---|
Description | String | Additional details about what the list is used for. |
Phone | String | The company's phone number |
PostalCode | String | The company's postal code |
StateOrProvince | String | The company's state or province |
TimeZoneCode | String | The list's time zone. Please use one of the TimeZoneCode codes provided by the method Get List of Time Zone codes. |
SmsSenderName | String | Default sender name for text messages. It can be a phone number (e.g. +393351234567) or a string (up to 11 chars, only letters and number). Please note that in some country, like Italy, some restrictions on SMS senders apply. Use MailUp admin console to verify if the specified sender is subject to limitations in some countries. |
DefaultPrefix | String | Default international prefix for mobile numbers (e.g. "0039" for Italy and "001" for United States) |
SendConfirmSms | Boolean | True when welcome SMS has to be sent for any new subscriber on SMS channel |
Charset | String | Text charset (see a list of Supported Charsets) |
Format | String | Format of emails to be sent with this list ("html" or "text") |
MultipartText | Boolean | Flag to automatically generate a text version of the message at sending stage |
KBMax | Integer | Message size beyond which a warning is generated. Suggested value = 100 |
NotifyEmail | String | Email address for unsubscribe notifications. Each time a recipient unsubscribes, an email will be sent to this address. |
OptoutType | Integer | Optout settings that apply when a recipient unsubscribe (0: One-click unsubscribe, 1: , 2: 3: Confirmed unsubscribe with options, 4: Confirmed unsubscribe with Preference Center) |
MultiOptoutList | String | Detail of the list IDs which will be viewed by the user in case of multiple optout (e.g. 1,2,3 etc.). Applies only when optout_type=2 |
SendEmailOptout | Boolean | When true a "goodbye email" is sent to recipient that unsubscribe |
SubscribedEmail | Boolean | True when welcome email has to be sent for any new subscriber (it works only when double optin is implemented) |
BouncedEmail | String | Address for error messages |
FrontendForm | Boolean | Enable hosted subscription forms, which you can view and edit under Settings > List settings > List Building Tools. |
Public | Boolean | Flag indicating if the list is visible in the public web library (if you set public=true the created list will be available in http://consoleUrl/frontend/nl_catalog.aspx) |
ScopeCode | Integer | select here which type of messages you are sending from this list:
|
TrackOnOpened | Boolean | True when link tracking has to be enabled at list level |
ConversionlabTrackCode | String | Code for tracking via conversionlab |
LinkTrackingParameters | String | It allows the integration between the list and third-party services (CRM, analytics). |
Old api method
Update List
Description | Update an existing list |
---|---|
HTTP Method | PUT |
URL | https://services.mailup.com/API/v1.1/Rest/ConsoleService.svc/Console/User/List/{List_ID} |
Reference | For details about parameters you can look at "Create List" method. |
JSON request (example) | { "Name":"New Arrivals", "description":"Use this list to inform subscribers about new products", "IdList":2 } |
JSON response (example) | |
Paging and filtering (example) |
|
Read Lists
Description | Return the lists that are visible for authenticated user. If an existing list is not returned it is likely that the MailUp specified with the API is not enabled to see that list. Users with administrators grants can change this setting using the admin console account (i.e. the web application) |
---|---|
HTTP Method | GET |
URL | https://services.mailup.com/API/v1.1/Rest/ConsoleService.svc/Console/User/Lists |
Reference | Go to automated doc |
JSON request (example) | none |
JSON response (example) | |
Paging and filtering (example) | 5 items per page, get first page (count starts from zero)
Retreive all the lists whose name contains 'Newsletter' filterby="Name.Contains('Newsletter')" and sort them by ID orderby="idList desc". Parameter names can be retreived from the response body. Please note that "Contains" is case sensitive.
|
Add recipients to a list - subscribe
You can use REST API to
- add and subscribe one or more recipients. See "Import recipients".
- force subscription of an existing recipient (i.e. unsubscribed or pending) by specifiying its ID. Refer to "Update subscription"
Remove recipients from a list - unsubscribe
REST API include either a method for single (refer to "Update subscription") or bulk (asynchronous import with "asOptout" option) unsubscription.
Trust your list's email addresses
When you create a list, you need to set two email addresses
- owneremail
- replyto
You should trust these email addresses for security reasons, so you can use TrustedSenders resource to do this job.
Trust an email address
Description | Use this method to trust a sender email address. Calling thie method, you'll send an email to the specified address containing a link to verify it. The response contains the value "StatusDescription": "Not confirmed (status: NotConfirmed)", "StatusCode": 0 because the sender email address hasn't been verified yet. When the sender I want to trust click the verification link, the platform trusts the sender and the StatusDescription (and the StatusCode) changes due to some platform checks. Please consider trusted a sender with StatusCode different from 0. You can use this method to re-request to trust a sender email address: in fact, every time you call this method, even if the address is verified, you'll receive an email containing the verification link and the platform updates the sender email address status to NotConfirmed. |
---|---|
HTTP Method | POST |
URL | https://services.mailup.com/API/v1.1/Rest/ConsoleService.svc/Console/TrustedSenders |
Reference | |
JSON request (example) | { "Email":"youremailaddress@yourdomain.eu" } |
JSON response (example) | { "AuthorizationDate": "", "CreationDate": "2016-11-28 12:34:36Z", "EmailAddress": "youremailaddress@yourdomain.eu", "IdTrustedSender": "ror11zuGscWcjl7m", "StatusCode": 0, "StatusDescription": "Not confirmed (status: NotConfirmed)", "UpdateDate": "2016-11-28 12:34:36Z" } |
Get trusted email addresses
Description | Use this method to retrieve the list of trusted senders' email addresses. | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
HTTP Method | GET | ||||||||||||
URL | https://services.mailup.com/API/v1.1/Rest/ConsoleService.svc/Console/TrustedSenders | ||||||||||||
Reference | |||||||||||||
JSON request (example) | None | ||||||||||||
JSON response (example)
| { "IsPaginated": false, "Items": [ { "AuthorizationDate": "2016-09-22 16:43:55Z", "CreationDate": "2016-09-22 16:43:45Z", "EmailAddress": "youremailaddress@yourdomain.eu", "IdTrustedSender": "ror11zuGscWcjl7m", "StatusCode": 0, "StatusDescription": "Not confirmed (status: NotConfirmed)", "UpdateDate": "2016-09-22 16:43:55Z" } ], "PageNumber": 0, "PageSize": 20, "Skipped": 0, "TotalElementsCount": 4 } The table below shows that you have to consider in your integration.
The table above does not display statuses that means Ok, your sender's email address is trusted! |
Get a trusted email address details
Description | Use this method to retrieve a trusted sender's email address details. | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
HTTP Method | GET | ||||||||||||
URL | https://services.mailup.com/API/v1.1/Rest/ConsoleService.svc/Console/TrustedSenders/{IdTrustedSender} | ||||||||||||
Reference | |||||||||||||
JSON request (example) | None | ||||||||||||
JSON response (example)
| { "AuthorizationDate": "2016-09-22 16:43:55Z", "CreationDate": "2016-09-22 16:43:45Z", "EmailAddress": "youremailaddress@yourdomain.eu", "IdTrustedSender": "ror11zuGscWcjl7m", "StatusCode": 0, "StatusDescription": "Not confirmed (status: NotConfirmed)", "UpdateDate": "2016-09-22 16:43:55Z" } The table below shows that you have to consider in your integration.
The table above does not display statuses that means Ok, your sender's email address is trusted! |
Disable an email address
Description | Use this method to disable a trusted sender. When you disable an email address, you cannot trust it again in the future. When you disable a sender, the trusted sender status is: "StatusDescription": "Blocked (status: Blocked)", "StatusCode": 2 If you need to re-trust an email address, please do not disable it, but call the method to Trust an email address to send the email containing the verification link again. | ||||||
---|---|---|---|---|---|---|---|
HTTP Method | DELETE | ||||||
URL | https://services.mailup.com/API/v1.1/Rest/ConsoleService.svc/Console/TrustedSenders/{IdTrustedSender} | ||||||
Reference | |||||||
JSON request (example) | For security reason, you need to submit the email address to disable using the If-match header.
| ||||||
JSON response (example) |
| ||||||
Groups
Create Group
Description | Create a group into the specified list. Group ID is returned |
---|---|
HTTP Method | POST |
URL | https://services.mailup.com/API/v1.1/Rest/ConsoleService.svc/Console/List/{ID_LIST}/Group |
Reference | Go to automated doc |
JSON request (example) | { "Name":"Test REST API Group", "Notes":"Notes should go here" } |
JSON response (example) | {"Deletable":true,"Name":"Test REST API Group","Notes":"Notes should go here","idGroup":30,"idList":2} |
Paging and filtering (example) | none |
Update group
Description | Update a group starting from group ID |
---|---|
HTTP Method | PUT |
URL | https://services.mailup.com/API/v1.1/Rest/ConsoleService.svc/Console/List/{ID_LIST}/Group/{ID_GROUP} |
Reference | Go to automated doc |
JSON request (example) | { "Name":"Test REST API Group renamed", "Notes":"I changed the notes again"} |
JSON response (example) | {"Deletable":true,"Name":"Test REST API Group renamed","Notes":"I changed the notes again","idGroup":30,"idList":2} |
Paging and filtering (example) | none |
Read Groups
Description | Read groups of specified list |
---|---|
HTTP Method | GET |
URL | https://services.mailup.com/API/v1.1/Rest/ConsoleService.svc/Console/List/{ID_LIST}/Groups |
Reference | Go to automated doc |
JSON request (example) | none |
JSON response (example) | |
Paging and filtering (example) | 5 items per page, get first page (count starts from zero)
Retreive all the groups whose name contains 'Test' filterby="Name.Contains('Test')" and sort them by ID orderby="idGroup asc". Parameter names can be retreived from the response body. Please note that "Contains" is case sensitive.
|
Delete Group
Description | Delete a group starting from group ID |
---|---|
HTTP Method | DELETE |
URL | https://services.mailup.com/API/v1.1/Rest/ConsoleService.svc/Console/List/{ID_LIST}/Group/{ID_GROUP} |
Reference | Go to automated doc |
JSON request (example) | none |
JSON response (example) | none |
Paging and filtering (example) | none |
Add recipients to a group
You can use REST API to
- add one or more recipients to a group and subscribe them to the MailUp list that contains the group. This double action is performed by a single operation, see "Import recipients" for details.
- add to a group an existing recipient by specifiying its ID. This operation also forces the subscription to the MailUp list of that group, refer to "Update group membership" for details.
Remove recipients from a group
REST API does not include yet a method for a bulk removal from a group, while the removal of a single recipient by specifying its ID is available. Refer to "Update group membership"
New to MailUp?
Click here to learn more about the difference between lists and groups in MailUp.