On this page:
Toc maxLevel 3
...
...
...
...
...
Comparison matrix
...
Use the tables below to compare these available solutions.
...
= available
...
| 
= available with restrictions (see specific notes for each case)
...
Manage lists and groups
| HTTP, Forms | SOAP | REST | SMTP+ | FTP | List+ | Frontend | |
|---|---|---|---|---|---|---|---|
| Create/Delete/Update lists |
...
| |
...
| Create/Delete/Update groups |
...
| |
...
| Read lists and groups |
...
...
| |
...
Manage recipients
| HTTP, Forms | SOAP | REST | SMTP+ | FTP | List+ | Frontend | |
|---|---|---|---|---|---|---|---|
| Import recipient (single) | | | | 1 | 2 |
...
| Import |
...
| recipients (bulk) |
...
|
...
Bulk import limit |
...
:
|
...
|
Bulk import limit:
|
...
|
...
|
Bulk import limit:
|
Bulk import limit: 10 MB |
...
| Force optin of unsubscribed recipient (single) |
...
| 2 |
...
|
...
(only with double optin) | 2 | |||
| Unsubscribe recipient (single) | | | |
...
| 2 |
...
Unsubscribe recipient (bulk) |
...
| |
...
| ||
| Subscribe with confirmed optin (COI) | |
...
| 10 |
...
| ||||
| Read personal data fields settings |
...
| |
...
| Update recipients' personal data fields | | | |
...
|
...
| Check recipient's subscription status | |
...
|
...
| Add to group (single) | | | |
...
| 2 |
...
| Add to group (bulk) |
...
| |
...
|
...
| Remove from group (single) |
...
|
...
| Remove from group (bulk) |
...
...
| 4 |
...
| HTTP, Forms | SOAP | REST | SMTP+ | FTP | List+ | Frontend | |
|---|---|---|---|---|---|---|---|
| Create email message |
...
| | |
...
|
...
| Read email messages |
...
| |
...
| Manage tags |
...
|
...
| Manage attachments |
...
| | |
...
|
...
| Manage both embedded and not embedded images in the same message |
...
|
...
| Manage dynamic fields |
...
| |
...
| |
| Manage dynamic |
...
| content |
...
| | |
...
| Manage image upload (i.e. make them hosted by MailUp) | | |
...
| ||
| Manage |
...
| attachments |
...
| |
...
| | ||
| Full content customization for each recipient |
...
|
...
| Allow mixing embedded and not embedded images in one email message |
...
|
...
| Transactional emails (account credentials after signup, password reminders...) |
...
| 5 |
...
| |
...
| Transactional emails (newsletters, customized messages) |
...
| 5 |
...
| |
...
| Promotional emails |
...
| |
...
| Send to a single recipient |
...
| | |
...
| 2,3 |
...
| Send to a group |
...
| |
...
|
...
| Send to all list subscribers |
...
| |
...
|
...
| Scheduled sending |
...
| |
...
| Manage queue of messages to be sent | | | |||||
| Get email statistics in real time |
...
| |
...
| ||||
| Get email statistics (with scheduled process) |
...
|
...
SMS
| HTTP, Forms | SOAP | REST | SMTP+ | FTP | List+ | Frontend | |
|---|---|---|---|---|---|---|---|
| Create SMS (with dynamic fields) |
...
| |
...
| 6 |
...
| Manage dynamic fields |
...
| |
...
| Send SMS to a recipient |
...
| |
...
| 6 |
...
| Send SMS to a group/list (immediate & scheduled) |
...
| |
...
| 6 |
...
| Get SMS statistics in real time |
...
| ||||
| Get SMS statistics (with scheduled process) |
...
...
|
Account provisioning
| HTTP, Forms | SOAP | REST | SMTP+ | FTP | List+ | Frontend | |
|---|---|---|---|---|---|---|---|
| New trial account activation | |
Other features
| HTTP, Forms | SOAP | REST | SMTP+ | FTP | List+ | Frontend | |
|---|---|---|---|---|---|---|---|
| Security |
...
...
| HTTP with encrypted querystring parameters |
...
| and IP restrictions9 available for several pages7 | HTTP, user authentication, and IP |
...
9 for MailUpImport web service
|
...
| HTTPS |
...
| only OAuth2 with refresh token |
...
| STARTTLS Encryption is supported | sFTP (port 22) is supported | Authorization workflow at application level (sender and mailing shall be approved before before sending) | HTTP with encrypted querystring parameters in most of the pages |
...
| 8 |
(1) New recipients are added to list when a message is sent to
...
them
(2)
...
This feature is designed for bulk operations, its massive use on single recipients may affect system performances
(3) New recipients are added when listed in enclosed "
...
one2many.import" file
(4) Requires a customization fee
(5)
...
SendSingleNewsletter method can be used for confirmation requests, not for massive use (see this Rate Limiting about
...
this method)
(6) With the "
...
...
sending from .CSV file" feature
...
...
Use cases
Synchronize recipients between your application and MailUp
...
You can use FTP Batch Processes for massive data transfer using files in CSV format. This feature can be used with very high numbers of recipients (import has been successfully tested with 4 millions of recipients in a single file) and it is configured on request by MailUp support team.
| Expand | ||
|---|---|---|
| ||
You can request this feature to
Data transfer is not in real time: it is usually configured as daily or weekly, hourly data transfer is feasible or it |
SOAP API
You can use MailUpImport SOAP API for an immediate import of recipients. You can use StartImportProcess method, eventually combined with NewImportProcess if the number of recipient is higher than 5000. These methods also allow a batch import as "pending", with the confirmation email that has to be manually sent using the adimin console account. SOAP API is not bidirectional, since it does not allow export of recipients.
SOAP API + FTP
You can get the best of FTP and SOAP API by using SendMessageNL API method, which performs scheduled sending to a group of recipients that is specified on a file. In this case you have to transfer the file to MailUp before calling the method. Export of recipients can be done with an FTP based integration.
REST API
Rest API allows immediate and bidirectional import and export of recipients. Due to restriction on HTTP channel, no more than 7MB can be uploaded with a single import. For export of recipient the paging feature is recommended to keep control on maximum size of tranferred data. REST API is the only MailUp solution that allows removal of a single recipient from a group
Webhooks
You can configure webhooks to enable a real time callback to your website when a recipient changes the subscription status or the personal data fields (e.g. by accessing to an autoprofile form). Callback method can be configured in order to include recipient's details as method parameter. Webhooks are managed by a worker process that is like a "frequent cron": you may experience some minutes of delay between the action and the corresponding callback.
Web forms
TODO.
Manage suppression lists
You can contact MailUp support and ask configuration of an FTP based integration with a batch process that is configured to run hourly. This process has to be set to import in a new group (group name = file name) the recipents that are listed in the file to be imported. Then, when you access to MailUp admin console, you can schedule your campaign to be sent to "all subscribers except for the recipients that belong to a certain group". It should be easy for you to identify the right group because it has the name of the imported file plus a timestamp.
Send email/SMS campaigns from your CRM
SOAP API
TODO
SOAP API + FTP
TODO
REST API
TODO
Send transactional emails/SMS
SOAP API
TODO
Read statistics
FTP
TODO
SOAP API
TODO
REST API
TODO
Frontend
TODO
...
(7) where these features are not available, the actions require a click on a confirmation email before proceeding
(8) please note that the purpose of frontend web pages is to be freely available by specifying an URL, without any console authentication
(9) Restrictions on caller IP cannot be used and shall be disabled in case of cloud hosting (in this case it is not possible to get all possible IPs to be authorized)
(10) Strong limitations apply. Check out this page for details and workaround