Compare API solutions
Available solutions
You can develop your integration with MailUp by mixing the available solutions and taking advantage of the various features they provide. Each listed item is a link to the correspondent documentation.
Recommended solutions
HTTP GET/POST (Subscription formsuse the same methods)
Other existing solutions (no longer extended, they may be deprecated in a near future)
On this page |
---|
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:
| 3 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 | HTTP, user authentication, and IP
| HTTPS only | STARTTLS Encryption is supported | sFTP (port 22) is supported | Authorization workflow | HTTP with encrypted querystring |
(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 "SMS sending from .CSV file" feature
(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